Moving from Jenkins to Bamboo, cant share artifacts between plans?

It appears that a generated artifact cannot be shared between plans. This is a strange limitation as it seems like a necessary feature for most users. For example I have a plan that generates a shared DLL that is referenced by several downstream projects. In Jenkins when the artifact is copied into another project, the change-log is shared with the downstream project so that you can see every change that affected the build and full traceability is achieved. Further individual builds can be promoted so that downstream builds can be built against a known stable version of a shared library and not necessarily the most recent build. There doesn't appear to be a way to achieve this functionality in Bamboo. How do you recommend handling shared libraries in Bamboo that lets me manage the version of the artifact to be used and provide full traceability?

1 answer

0 votes

Passing artifacts between Plans is something we want to add soon, though the exact plan is not set in stone yet. Please vote on the issue here:

Until then workaround is to download an artifact from Bamboo Server when needed, for example using Script Task + wget.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

185 views 4 1
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you