We haven't gotten to this yet but we will. Let's discuss tomorrow. /KenY On 2018-12-19, 4:23 PM, "Victor Rodriguez" <vm.rod25@gmail.com> wrote: Ken Any update on this? Do you still need this script for the CENGN release notes/changelog? Can we discuss this topic on tomorrow build meeting? Regards On Thu, Dec 6, 2018 at 10:56 AM Ponce Castaneda, Guillermo A <guillermo.a.ponce.castaneda@intel.com> wrote: > > Hello everybody, > > I want to share with you the following script that we use internally to create a Change Log everytime we generate a new StarlingX ISO. > Here, internally, we have a Jenkins server that creates (or tries to) a new ISO every day, and with this ISO we also create a manifest.xml file, and by using another job that is triggered just as the ISO Job finishes we create the Change Log by using the following script: > https://gist.github.com/gaponcec/99f19e2bc972761e11ccba2260622d10 > > The script has the following requirements: Argparse, gitpython, xmljson, dictdiffer and PTable. > It requires two parameters, the old manifest.xml and the new one and it should be run like this: > $ python3 create_change_log.py-o old_manifest.xml -n new_manifest.xml > > This will give you the change log on stdout. > > On our Jenkins script we save a file with this and e-mail it to the team afterwards. > > Please let me know what you all think about, feedback is really appreciated. > > - Guillermo Ponce > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss@lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss