Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to show proper changeset in a bamboo release plan

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?

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo Data Center on Kubernetes

Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...

56 views 0 3
Read article

Community Events

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

Events near you