Errors in Artifact Download task after changing Build key
Problem
After moving a Build plan and changing its key, you may see the following errors in the atlassian-bamboo.log when exporting the plan as Specs:
2018-01-10 14:05:51,953 ERROR [http-nio-8443-exec-190] [ViewPlanSpecs] Chain PROJ-PLAN does not exist.
com.atlassian.bamboo.specs.api.exceptions.PropertiesValidationException: Chain PROJ-PLAN does not exist.
at com.atlassian.bamboo.plugins.artifact.export.ArtifactDownloaderTaskExporter.toSpecsEntity(ArtifactDownloaderTaskExporter.java:180)
at com.atlassian.bamboo.configuration.external.helpers.TaskDefinitionExportHelper.toSpecsEntity(TaskDefinitionExportHelper.java:53)
at com.atlassian.bamboo.configuration.external.PlanConfigExportServiceImpl.lambda$null$13(PlanConfigExportServiceImpl.java:299)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)Cause
This appears to be caused by the task retaining the old build key in its configuration.
Resolution
This can be resolved by following the steps below.
Given a Build plan with key PROJ-PLAN, that had been changed to PROJ-MYPLAN:
- Go to the Plan configuration for PROJ-MYPLAN
- Check for any Artifact Download Task
- Check the source plan for any references to the name for PROJ-PLAN?
- If so, please select the new name of PROJ-MYPLAN
- Retry the export to Bamboo Specs
Last modified on Jan 11, 2018
Powered by Confluence and Scroll Viewport.