Issue Summary

Currently, Bitbucket Pipelines has a flag to disable the download of the previous step's Artifacts, which is documented here:

When enabling download: false, Pipelines should ignore the previous' step artifacts and not download any of them in the step where this is set.

If this flag is set on a manual deployment step, and the artifact expires (14+ days pass, so the artifact is no longer available), even though the deployment step has the flag set, you will not be able to deploy, you should see that the button to deploy is greyed out with the message "Artifacts have expired".

Steps to Reproduce

• Set up a pipeline that produces artifacts and has some manually triggered deployment steps.
• For those manually triggered steps, set download: false on the artifacts property.
• Wait for the artifacts to expire (14 days), then try to click on the "Deploy" button. You should see that the deploy button will be greyed out, with the message "Artifacts have expired".

Expected Results

The Deploy button will be clickable regardless of the state of the artifact, as steps with the download: false option will not download the artifact in any way.

Actual Results

Currently, if a build has Artifacts in them, and those artifacts expire, you will not be able to click on the deploy button, even if the download: false flag is set for that step.

Workaround

Rerunning the entire build should allow you to click on the deploy button. This is not ideal as it would take both additional time and build minutes.