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:
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?
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.
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
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