I have read Sharing artifacts Sharing artifacts between build plans section and been wondering how the artifacts versions are managed.
For example, I have two build plans. Plan A produces a jar file upon each run, and B produces a war file upon ear run. Then I have a master plan which downloads the artifacts of A & B, and then generate a ear file.
A & B are triggered automatically on each code commit, while master plan is run manually. In this case each time I run the master plan, it always gets the latest version of artifacts from A & B, doesn't it? Is there a way to specify the version of artifacts to be downloaded?
Any comments / suggestions are appreciated. Thank you.
As stated in the documentation you mentioned:
The artifact from the most recent successful build will be used. If there are no successful builds from the artifact-producing plan or the artifacts have expired, the artifact-consuming job will fail.
So yes, the "Artifact Download task" will always use the war file produced by the latest plan A and B successful builds.
This is the current behavior but there is an open improvement request asking for the ability to download shared artifacts from specific builds:
I encourage you to vote on and watch the Improvement Request to increase its visibility and ensure you're kept in the loop with any future updates.
...roperties: -Dbamboo.bitbucket.cloud.use.workspace.api=true There are patches available for Bamboo versions 6.8.3, 6.9.2, and 6.10.5 on the bug report that add support for the System Property. T...
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