I downloaded and tested the new Bamboo 4.0.
Unfortunately, it seems not correctly to work in regard to the Revision number in the Build Result Summary.
The problem recreation procedures are as below.
1. Create a Plan which has a single repository.
The repository URL is as below.
On the Subversion side, there is another repository under the same trunk as below.
The latest revision number in the AccountWeb is 14.
On the other hand, that in the OrderWeb is 18.
The Plan has only AccountWeb, not OrderWeb.
2. Go through [Plan] -> [History] -> [Build Result Summary] -> [Revision].
The expected number is 14, not 18.
But the Bamboo 4.0 displays 18.
The Bamboo is mixed up with the right repository.
In fact, [PLAN_VCS_HISTORY]->[REVISION_KEY] is 18 in the underlying databse.
I suspect this problem happens the Bamboo searches in the same trunk with the new functionality
of Branches and records the wrong revision number of another repository that exists in the same trunk
but is not configured in the Plan.
What do you think of the issue?
I want to know a workaround if there is.
Good news, I decided to create a plug-in to allow proper use of repository related properties when using multiple repositories on one plan. It allows you to specify a prefix per repository which is then applied on each property which allows you to access each property for a particluar repository independently.
It is enlisted in Codegeist, please vote :-)
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