Using Bamboo, our build jobs compile version numbers into our actual program (We build an APK for Android) and also modify some other data files with the version number. The version number is generated via variables in the plan.
Deployment is confusing. You deploy previously completed builds, but Deployment Project settings also allow you to setup a versioning scheme. Why does the build process not use a versioning scheme? The Deployment project does not initiate a brand new build to use the scheme, so what is the purpose of the versioning settings in the deployment project? Those wouldn't be used since we already setup our version number during the build steps.
IMO, the end to end functionality of Bamboo's deployment projects just wasn't thought out very well. It leaves users wanting so much more and I'm not talking about bells & whistles. Seems it wasn't created with a users perspective in mind, which makes it extremely frustrating to use.
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