Cool. I can simply strip off all the headers in a 1-line script and I'm left with something usable as a standard changelog. Thanks!
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Christopher Orr Sent: February-26-15 13:57 To: [email protected] Subject: Re: Script to extract the git commit messages? On 26/02/15 08:15, John Mellor wrote: > I'd like to extract the git commit messages for the changes since the last > build, and insert them into the debian changelog in the product. This will > in many ways make each build self-documenting, and does things in a way that > is already very well supported when building .debs. > > Has anyone done this? The SCM changes since the last build are stored with the build and can be retrieved, for example, from the API during a build, e.g.: http://jenkins:8080/job/$JOB_NAME/$BUILD_NUMBER/api/xml?wrapper=changes&xpath=//changeSet//comment That would give you an XML document with each commit message in a separate tag. See also: http://stackoverflow.com/a/11837662/234938 Regards, Chris -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/54EF6C97.4070501%40orr.me.uk. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c53ff83dec464301a37f725c7c257535%40mbx01colo01p.esentire.local. For more options, visit https://groups.google.com/d/optout.
