Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is it possible to version the artifact sharing definition along with code?


Bamboo is using the latest definition of artifacts in the Deploy step "Artifact Download": "All artifacts" rather than using the definition based on the CI at the time and therefore failing to deploy an old build if a newer build has introduced a new artifact.

To explain this further:

  • Build 1 creates shared artifact A -> Release 1 downloads all artifacts and gets artifact A 
  • Build 2 creates shared artifact A + B -> Release 2 downloads  all artifacts and gets A + B
  • Deploy Release 1 again, this now fails because artifact B doesn't exist in Build 1

It is difficult to work out how to change the CI to be compatible again with release 1 and keep track of the changes for release 2. 

Instead it would be good if there was a mechanism to define the artifact definition in code/xml/json etc. that is versioned along with the rest of the code in the build. Is this possible today?

1 answer

0 votes

You can achieve this by migrating your entire Bamboo plan configuration to Bamboo Specs, which precisely aims to "store build plans configuration as code". Job artifacts are supported in both the Bamboo Specs (Java) and the Bamboo Specs (YAML) flavor, but please note that the former offers considerably more encompassing feature coverage for the time being.

Once you have migrated your plan configuration to Bamboo Specs (you can get started by exporting the current one), you might also want to consider setting up "Repository-stored Specs" so that you can "automatically build and execute Bamboo Specs on every push you make to a Git repository", see Enabling repository-stored Bamboo Specs.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events