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

Michael Fowler February 24, 2013

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
Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 25, 2013

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: https://jira.atlassian.com/browse/BAM-10573

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
TAGS
AUG Leaders

Atlassian Community Events