On Tuesday, June 14, 2016 at 3:16:23 PM UTC-6, John O'Brien wrote: > > I had a user of our Jenkins system pose the following problem to me: > > > ------ > > 1. A new build is started with changes. > 2. Note the changes are documented in the build description on Jenkins. > 3. Build fails in this scenario > 4. Start a new build > > > Result: New build shows no changes. Technically it does have changes as > there hasn't been a successful build with the changes yet. > > > This situation has lead to a lot of miscommunication between PMs/QA and > engineering as we are utilizing the Jenkins post build script to update > tickets with build numbers. > > ------ > > > I'm drawing a bit of a blank as to what could be causing this and wanted > to reach out to the community. > > > The git plugin (as one example) reports changes (by default) from the preceding build, independent of the status of the preceding build. I prefer it that way because then the commit which fixed a broken build is obviously the only change shown in the list of changes.
There is a setting in the git plugin which will allow the plugin to always compute changes against a specific branch. I use that setting in those cases where I'm using a job to evaluate a proposed change to a base branch. Mark Waite > Thanks in advance for any suggestions! > > > -John > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7facb725-3b40-4119-a770-78adb304a388%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
