Details
-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Customer use case;
While using Bamboo with the BRMP plugin to trigger "release builds".
During the release builds, we would like the build script to automatically update the "version" of our Maven POMs (using the Versions Maven plugin), and commit these changes to our Git repository, so that the release build is reproducible.
I have implemented all this in our build plan, but the problem is that Bamboo captures the commit ID at the start of the build, and does not update its records with the new post-commit commit ID. This has two consequences:
- the commit ID recorded with the build does not match the actual code used for the build
- Bamboo then triggers another build because it detects a commit after the one that triggered the build.
Attachments
Issue Links
- is related to
-
BAM-18746 Allow Bamboo to update Revision if checkout is made via script task mid-Build
- Gathering Interest