I've created a "release" plan in bamboo that is triggered manually whenever we want to publish a new release of software.
This plan, does the typical things, it checks out code, builds it, tags it, and publishes the artifacts.
The problem is, bamboo stores the git revision at the start of the job. Since this is a release job, there is a commit that occurs at the end.
On the results page of a successful build in bamboo, it figures out what jira tickets, changesets, etc are in a build based on this git revision. Since it uses the revision at the start of the job instead of at the end of the job, these details are always 1 release back.
IE, release 2 shows the changeset that was in release 1. When you build release 3, it would show the changeset that was in release 2.
Is there a way to tell bamboo to change the revision it links to a given build? Some script task that can be run after the commit to get the revisionID and update the build with it?
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs