[BAM-20072] Bamboo Specs fails to deploy deployment projects associated to plan branches, with an SCP task receiving an artifact from the plan branch.

Type: Bug
Resolution: Timed out
Priority: Low
Fix Version/s: None
Affects Version/s: 6.6.2
Component/s: Bamboo Specs
Labels:
- bamboo-bugs-grooming
- da-warranty

Support reference count:
1
Symptom Severity:
Severity 3 - Minor
Bug Fix Policy:
View Atlassian Server bug fix policy

Summary

Bamboo Specs fails to deploy deployment projects associated to plan branches, with an SCP task receiving an artifact from the plan branch.

Steps to Reproduce

Create a build plan with a job that generates an artifact.
Create a plan branch (that also generates an artifact).
Create a deployemnt project associates to the plan branch.
In the environment, create an "Artifact Download" Task that downloads the artifact from the plan branch.
In that same environment, create an "SCP Task" that manipulates the previous artifact.
Export the deployment project using Specs.
Import the Specs Java file.

Expected Results

An environment as the one manually created.

Actual Results

Specs deployment fails with the following error:

2018-09-03 09:33:41,389 INFO [BambooServer] Publishing deployment proj2
Exception in thread "main" com.atlassian.bamboo.specs.api.exceptions.BambooSpecsPublishingException: An error occurred while publishing deployment proj2: Environment 'env2' / SCP task / Artifact: SCP Task expects an artifact 'PR1-PL1: artifact' but no Artifact Downloader task provides it.
	at com.atlassian.bamboo.specs.util.BambooServer.translateRestException(BambooServer.java:170)
	at com.atlassian.bamboo.specs.util.BambooServer.translateException(BambooServer.java:140)
	at com.atlassian.bamboo.specs.util.BambooServer.publish(BambooServer.java:97)
	at Specs.PlanSpecBSP39580.main(PlanSpecBSP39580.java:73)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
Caused by: com.atlassian.bamboo.specs.exceptions.BambooSpecsRestRequestException: Environment 'env2' / SCP task / Artifact: SCP Task expects an artifact 'PR1-PL1: artifact' but no Artifact Downloader task provides it.
	at com.atlassian.bamboo.specs.util.RestHelper.lambda$sendRequest$2(RestHelper.java:89)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:222)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:164)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:139)
	at com.atlassian.bamboo.specs.util.RestHelper.sendRequest(RestHelper.java:92)
	at com.atlassian.bamboo.specs.util.RestHelper.post(RestHelper.java:201)
	at com.atlassian.bamboo.specs.util.SendQueue$1.run(SendQueue.java:23)
2018-09-03 09:33:42,252 INFO [BambooServer] An error occurred while publishing deployment proj2: Environment 'env2' / SCP task / Artifact: SCP Task expects an artifact 'PR1-PL1: artifact' but no Artifact Downloader task provides it.

Workaround

In scenarios like this one, avoid using Specs. Creating and editing the project/environment from the UI will work properly.

Martyna Wojtas (Inactive) added a comment - 23/Jun/2020 3:09 PM

Atlassian Update - 23 June 2020

Hi,

Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.

Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

Thank you,

Bamboo Team

Martyna Wojtas (Inactive) added a comment - 23/Jun/2020 3:09 PM Atlassian Update - 23 June 2020 Hi, Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Bamboo Team

Details

Description

Summary

Steps to Reproduce

Expected Results

Actual Results

Workaround

Attachments

Forms

Activity

Collapse comment: Martyna Wojtas (Inactive) added a comment - 23/Jun/2020 3:09 PM

Expand comment: Martyna Wojtas (Inactive) added a comment - 23/Jun/2020 3:09 PM

People

Dates