Artifact download fails if version/release is not deployed before expiry

Summary

• Expiry logic will remove artifact (row in database) from deployment version if version/release is not deployed.

Environment

• Bamboo Global Expiry
  • Expire after 3 days
  • Minimum builds to keep 5
  • Minimum deployments to keep 5
• Bamboo Plan Expiry
  • Build results, Build artifacts, Build logs Expire after 35 days
  • Exception: Min Builds to keep 20 builds per plan

Steps to Reproduce

• Run build that publishes a shared artifact
• Create a release of this build
• Run several other builds
• Deploy release after 10 days or more, for instance

Expected Results

• Artifact download task should be able to download the shared artifact

Actual Results

• Artifact download task fails, unable to find artifact

  simple	28-Apr-2017 12:12:57	Preparing to download plan result PROJ-PLAN-17 artifact: Shared artifact: [Artifact], pattern: [Foo.txt] anchored at: []
  error	28-Apr-2017 12:12:57	Unable to download artifact Shared artifact: [Artifact], pattern: [Foo.txt] anchored at: []
  simple	28-Apr-2017 12:12:57	Task configuration:
  simple	28-Apr-2017 12:12:57	artifactName_0 -> [Artifact]
  simple	28-Apr-2017 12:12:57	artifactId_0 -> [75224803]
  simple	28-Apr-2017 12:12:57	sourcePlanKey -> [PROJ-PLAN]
  simple	28-Apr-2017 12:12:57	localPath_0 -> []
  simple	28-Apr-2017 12:12:57	Task runtime configuration:
  simple	28-Apr-2017 12:12:57	securityToken -> [cdb294c307f3b2179c704913183cbf1dabaf1ba8]
  simple	28-Apr-2017 12:12:57	runtimeArtifactIds_0 -> [0]
  simple	28-Apr-2017 12:12:57	artifactName_0 -> [Artifact]
  simple	28-Apr-2017 12:12:57	artifactId_0 -> [75224803]
  simple	28-Apr-2017 12:12:57	resultKey -> [PROJ-PLAN-17]
  simple	28-Apr-2017 12:12:57	artifactLocation_0 -> [subfolder]
  simple	28-Apr-2017 12:12:57	localPath_0 -> []
  simple	28-Apr-2017 12:12:57	artifactPattern_0 -> [Foo.txt]
  

Notes

• Build PROJ-PLAN-17 and its artifact are still available from Bamboo's UI
• No record returned when running SQL statement:

  -- get deployment/environment consuming artifact
  select DEPLOYMENT_VERSION_ITEM_BA.PLAN_KEY
       , DEPLOYMENT_VERSION.PLAN_BRANCH_NAME
       , DEPLOYMENT_VERSION_ITEM_BA.BUILD_NUMBER
       , DEPLOYMENT_RESULT.AGENT_ID
       , QUEUE.AGENT_TYPE
       , DEPLOYMENT_RESULT.ENVIRONMENT_ID
       , DEPLOYMENT_ENVIRONMENT.NAME
       , DEPLOYMENT_ENVIRONMENT.XML_DEFINITION_DATA
       , DEPLOYMENT_VERSION_ITEM_BA.*
    from DEPLOYMENT_VERSION_ITEM_BA
    join DEPLOYMENT_VERSION_ITEM on DEPLOYMENT_VERSION_ITEM_BA.VERSION_BAM_ARTIFACT_ITEM_ID = DEPLOYMENT_VERSION_ITEM.DEPLOYMENT_VERSION_ITEM_ID
    join DEPLOYMENT_VERSION on DEPLOYMENT_VERSION_ITEM.DEPLOYMENT_VERSION_ID = DEPLOYMENT_VERSION.DEPLOYMENT_VERSION_ID
    join DEP_VERSION_PLANRESULTKEYS on DEPLOYMENT_VERSION.DEPLOYMENT_VERSION_ID = DEP_VERSION_PLANRESULTKEYS.DEPLOYMENT_VERSION_ID
    join DEPLOYMENT_RESULT on DEPLOYMENT_VERSION.DEPLOYMENT_VERSION_ID = DEPLOYMENT_RESULT.VERSION_ID
    join DEPLOYMENT_ENVIRONMENT on DEPLOYMENT_RESULT.ENVIRONMENT_ID = DEPLOYMENT_ENVIRONMENT.ENVIRONMENT_ID
    join QUEUE on DEPLOYMENT_RESULT.AGENT_ID = QUEUE.QUEUE_ID
   where DEPLOYMENT_VERSION_ITEM_BA.BUILD_NUMBER = 17
      and DEPLOYMENT_VERSION_ITEM_BA.PLAN_KEY like 'PROJ-PLAN';
  

Workaround

1. Delete the release exhibiting the issue
2. Re-create the release