I have two deploy environments: test and production. Bamboo requires to make releases before deploying to any of it. But for test environment I do not want to make release. How can I achieve it?
This leads to multiple version autoincrement between "real" releases, and disallows any possibility to plan next "real" release version. Another way is disable version autoincrement when releasing build and set versions manually, but I wish bamboo makes this automatically after "real" release.
As Alexey said, you can go for different release numbers in Test and Prod. But there is another way you can think of it.
Ideally, you do not have to create a separate release for Test and Prod. You create a release for Test, and test it. Once it looks good, you approve the release and promote it to production. In this case, Test and Production are two environments in the same deployment project.
By doing this, you might have release-1, 2 and 3 in test but you might end up promoting only release-3 to Prod.
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