Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to setup parent plans

I have a C++/Qt project for which a release is a combination of 6 different builds which all run as different plans because they target different platforms (i.e. win32, win64, macx etc etc). I have setup a parent plan which allows me to trigger the corresponding child plans: e.g.

Project Plans:

build-production-all (does nothing, then invokes the above builds using child plans)

How do I get the parent plan to wait on the completion of the child plans so I can download the artifacts created and make them available for a deployment plan? OR

How do I get a deployment plan with multiple build plans as input to ensure the artifacts from its dependent plans are build from the correct git hash?

In an ideal world, it would be able to trigger a release from JIRA, calling the correct parent build plan (build-[production, beta etc]-all), and then have a single deployment plan which i can hit release on which works if all platform plans build successfully. I cannot see how to make that happen (?)

I then want to replicate this for different branches, some using branch plans, some using explicitly separate plans (differences in scripts which need calling etc), but I think that would be easy if I can work out how to do it for one branch.

Any help would be appreciated, it seems like several points in this workflow are just not supported at all!


1 answer

0 votes
Foong Atlassian Team Nov 06, 2018

Instead of different Plans, how about using different Jobs inside a single Plan for each environment build?

Each Job can be configured to have certain requirement so that different agents from different environments will build it.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events