This should be baked into the baseline Jenkins functionality. However here's a possible workaround:
I have a similar issue with tfs plugin. It appears Jenkins does not list commit message in recent changes during the first build. However...There is a file called "changelog.xml" in the build that can be manipulated via scripts (or manually). I often "customize" Jenkins by manipulating the xml files with some simple scripts. On Thursday, March 21, 2013 3:53:09 PM UTC-4, Brian Jones wrote: > > Kevin, > > I agree with you. How can that be implemented? > > All, > > It appears to me that Jenkins does not work well with this use case: > > * master HEAD is release version 1 (v1) of product. > * 4 features ABCD that are implemented on git branches ABCD respectively > based on v1 > * Jenkins project to build every branch > * Changes are implemented with one commit per branch (developers are > exceptional) > * Changes are merged without conflict to master as version 2 (v2) > > How do I get Jenkins to tell me that v2 contains JIRA issues ABCD without > scripting this myself? The git plugin does not see any changes when ABCD > are built and when v2 is created. Am I outside the assumed use cases of > Jenkins/git here? > > Brian > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
