Degraded performance Customers may experience issues using Community search. Our team is investigating.
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?
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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