Our release process is such that in the begining of a release cycle, the release vehicle (aka release version number) is undetermined. A temporary codename is used as the release version.
As we get closer to Feature freeze, the official version is finalized and we need to update the build plan from it's code version to the official version.
There is a functionality in bamboo to "move" the build plan from one version to another version. However, as part of this move, changelist info on the build summary page , since last build before rename, seems to be lost.
Is this a known issue?
We use perforce as our source code repository. It will be great if there's a way to rename build plan version without incuring missing changelists in the 1st build after the switch.
Steps to replicate the issue:
1. Administration>Plans>move plans
2. Destination Project: New Project
Project Name: <enter new project name>
Project Key: <enter new project key>
3. Check the plan to move
4. click 'move' button
5. provide new name and key
6. click 'done'.
7. Run the new plan.
8. Build summary does not list out the changelists since the last change.
bamboo version: 4.4.5
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot