We have a bamboo plan using a git repository -- The plan is configured to check out master by default.
During the plan, it merges another branch into master, updates the version and commits a new tag. This makes new commits into master.
What I'd like is the plan summary page once it is complete, to reference this new git commit #.
However, regardless of what I try, it only ever references what initially triggered the plan. Because of this, the list of commits and linked jira issues all reference the old version on master instead of the new version that was just created/merged. So for example if this is created releases (release 1, release 2, release 3, etc) then the summary page for the release 2 build, contains all the info for release 1 (because it points to the release 1 git revision #), and once release 3 is done, then that page points to release 2, etc.
I've tried making a second child plan that is triggered at the end, but this child plan carries over and checks out the previous revision too and will not update to the latest.
Is there any suggestion on how to do this? I imagine multiple people in the community do merges as part of their build plan and want the build pages to indicate the actual set of changes based on the commits after that merge.
Since child plans inherent the revision number from the parent -- I was unable to split it into two plans to get the information correct. Is there some other way to achieve this?
We’re preparing for Bamboo 8.0, which will be our first Data Center release. To make sure our app vendors and customers with written in-house apps are prepared, we’re launching Bamboo 8.0 Early Acces...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events