Here is what I am trying to achieve
Plan A - run on every checkin, and generate artifacts
Plan B - runs on every checkin, and generate artifacts
Plan C - runs on every checkin, and generate artifacts
Plan D - runs Plans A, B, C nightly. Gathers artifacts from all three plans. Order is not important
Development plan - Takes artifacts from Plan D and issues a release
I am not able to figure out how to get Plan D to get the artifacts from Plan A, B and C. I added them as dependencies, but they run after Plan D is completed.
I read that you can add the plans as a stage, but how I am unable to figure out how to do this ??
Any ideas on a best way to solve this.
The instructions for sharing artifcats between Build Plans are described on the documentation below. There is no need to create dependencies. You just have to make sure that the artifacts generated by Plans A, B, C and D are shared and that you use a task called 'Artifact downloader' to perform the action. Have a look at the details at the doc:
Hope it helps.
Thanks, but I have gone through that document several times and I still do not see the expected behavior. For simplicity, I created a Plan A that generates a shared artifact and a Plan B that users the artifact downloader to access Plan A artifacts, but I do not see these artifacts show up when Plan B finishes. I have a Deployment plan which takes the artifacts from Plan B, but I don't even see it there either.
Okay, I finally figure this out. I was not exposing the artifacts in my Plan B (above example).
I am now trying to figure how to run a plan in a dependency list after all plans have succeeded.
Plan A - Agent 1: Parent plan that has the following dependencies
Plan B - Agent 1
Plan C - Agent 2
Plan D - Agent 2
Plan E - Agent 1. Collects artifacts from Plan B, C, D. But runs ONLY after Plan B, C, D are complete.
Since the plans run on different agents, Plan E runs immediately after Plan B is finished, but I want it to wait till both Plan D and C are done.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot