It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I reference multiple build plans in deployment project

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.

 

4 answers

1 accepted

2 votes
Answer accepted

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.

We ended up using this approach as well. Big downside of this approach is that when you want to make any change to the secondary build plan(s), you need to kick off the entire build pipeline

I am embarking on the same situation as the OP, any experts have some opinions?  As of now I have to have separate "deployment" projects 

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 ?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Unable to add or edit Bitbucket Cloud repository in Bamboo

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...

1,144 views 2 7
Read article

Community Events

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

Events near you