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.
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events