I am new to deployment project, and this is the workflow I am thinking about:
* Bamboo building continuously, and when I like a release, I go to Deployment project and create a new release (say v10)
* v10 contain 20 commits, and 3 issues
* now I figured I dont' want to deploy v10 to production, so I create v11
* v11 is next build containing 2 commits and 1 new issue
How do I capture the next production release contains 22 commits and 4 issues, rather than 2 commits and 1 issue?
- if you deploy manually, the 'run deployment' screen will compare the currently deployed version with the version that is currently deployed
- in version page, you have tabs for commits and jira issues, when you go there you can select any version from the history and see agregated commits and issue since that version
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