Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
1
-
Description
Problem Definition
Currently, Bamboo only updates the "Revision" in the Build Result Summary if the checkout is done in a Source Code Checkout Task. If checkout is done in a script Bamboo will only report the checkout done in the initial VCS checkout.
Suggested Solution
Add an option for Bamboo to update the VCS revision ID outside of VCS Checkout Tasks.
Why this is important
Working around some limitations, such as Gatekeeper functionality from Jira builds, requires running checkouts and commits in a Script task. This currently reports an old revision.
Workaround
Depending on your use case, Gatekeeper or Branch Updater may work as a workaround. This does not work when builds are triggered from Jira, since those builds only run the default/master branch.
Attachments
Issue Links
- relates to
-
BAM-9226 Ability to change VCS Revision number after a build is finished
- Closed