I'm attempting to retrofit a continuous deployment pipeline onto our existing Bamboo CI infrastructure. For us, a "release" consists of a set of several Wars built by several different build plans.
It seems like a Bamboo deployment project can only reference the artifacts from a single build plan. For us, getting all the different artifacts under a single build plan feels impossible.
I'd like to aggregate build X of plan A, build Y of plan B, and build Z of plan C and call that "Release N".
Any way to do this? (I'm using 5.7.2) I tried making an aggregator build plan and copying the artifacts from several plans, but that method loses all references to what build the shared artifacts came from.
I found this article helpful - http://blogs.atlassian.com/2013/10/sharing-artifacts-between-plans-and-other-best-practices/
Essentially, in your primary build plan you need to download the artifacts from all of your other build plans, then republish the artifacts again. Now your primary build plan contains all of the artifacts from your other builds, and your deployment job can access any/all of the artifacts.
Same problem, it is troublesome to have multiple Deployment project tho, because 1) we need to remember to deploy together during deployment, and 2) in case of issue, we need to remember to roll back both projects.
On top of this, our system is quite complex, these inter-dependency is not the same during every release.
Same issue here, my Build Project contains multiple build plans that build various sub-components of our product from different svn repos. These components are dependent on each other for build purposes and bamboo dependencies work well for triggering the rebuild of components when something they build against changes. But to deploy a release we need to deploy all the components, from about 40 build plans. How do you suggest we configure a Deployment project to collect and deploy the artifacts from these 40 Build Plans ?
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