Problem

Any generated build artifacts references/locations are expected to be updated on the database when rerunning a plan. Deployment plans will refer only to the original artifact metadata and fail to download them when the original plan's artifacts were expired and later recreated by a rerun.

Environment

Bamboo 7, 8

Steps to Reproduce

1. Create a Build plan with a shared artifact
2. Create a Deployment plan that would consume the artifact
3. Create and run a Deployment Release
4. Configure Expiry settings to "Build and release artifacts only" so only the plan artifacts would expire
5. Expire the Plan's artifact
6. Rerun the Plan that had its artifact expired to recreate the artifact - validate that it was created and is downloadable through the UI
7. Try redeploying the same release

Expected Results

1. The Deployment Release should understand the new artifact location/Ids and succeed; OR
2. The build Plan should not allow reruns when linked to a Deployment to avoid the false impression that recreated artifacts will be normally used by Deployments; OR
3. Bamboo should allow the user to override the static build/artifact requirement on Deployments and use newly built artifacts from the same build number

Actual Results

The Deployment release fails to download the artifact

Workaround

Run a new build based on the same code revision used by the old build and create a new release based on the new run:

1. Open the old Build # results page and locate the "Revision" number. Copy it to the transfer area
2. Run a new Build: Build plan -> Run -> Run Customised -> Revision -> Paste the git revision from the old Build #
3. Run a new Deployment Release based on the new Build