Artifact dependencies with YAML specs

[Rene Wittmann]

I have a build plan that needs the artifacts of another plan. The plan generating the artifacts is in YAML specs, so I'm not able to setup the artifact using plan as child plan.

Are there any options to work around that?

I can set a trigger on Plan fail, but not on Plan pass, so this will not help without inverting the logic in the generating plan.

Is there a plugin that could help?

Any recommendations are highly welcome.

[Rene Wittmann]

Well I guess upgrading to Bamboo v.8.1.2 should be sufficient...

[Shashank Kumar]

Hello Rene,

Welcome to Atlassian community

You can use the Artifact download task to achieve the same and choose the plan from where you want to download the task, see the example below

YAML Specs code

- artifact-download:
artifacts:
- {}
source-plan: BAM-SHA

You have said upgrading to Bamboo v.8.1.2 should be sufficient, hope you are talking about the above 2 solutions.

Regards,

Shashank Kumar

**please don't forget to Accept the answer if your query was answered**

[Rene Wittmann]

Sorry, no.

Your suggestion does not help: without defining the dependency with parent and child plan, the plan using the artifact will start as soon as an agent is ready to build the plan.

And it will then use the artifact that is available from the "parent", no matter whether a more convenient artifact (e.g. the artifact that is based on the same commit id) is available later.

[Shashank Kumar]

Hello Rene,

Let me try to understand the flow and you can correct my understanding

1. Plan A is the plan which generates the artifacts - This plan is created via YAML Specs RSS.

2. Plan B needs the artifact generated via Plan A .

Requirement:

1. You want to create Plan B as a child plan of Plan A via YAML code ( so basically you require YAML logic to define the child dependency ?)

This is because When you run Plan A it creates an Artifact and immediately Plan B should be trigerred which should use the same artifact generated.

Let me know if this is the flow you are targeting.

Also what is your current Bamboo version ?

Regards,

Shashank Kumar

[Rene Wittmann]

Exactly, this is the aim.

Previously, I used Bamboo version 8.0.5.

With that version it was not possible to define Plan A as parent plan of Plan B.

So now I updated to Bamboo version 8.1.12. This version contains an update of YAML specs where I can define the dependency between Plan A and Plan B.

[Shashank Kumar]

Cool, I was testing this on Version 9 so was wondering Why you are not able to see this option.

Anyways you have already upgraded!