Can a branch plan be dependent upon another plan?

[Kevin Loveland]

This comes from one of my collegues:

Can a Plan be set as dependent on another plan than that is based on a branch. For example, we have a CI build that is based on trunk and a Release build based on trunk from the SVN SCM. Each plan has specific stages and jobs underneath them. When the CI build is complete, the Release build is triggered.

We have recently add a branch under the CI build. We noticed there is no branch-specific configuration for the branches. We would like to have a Release plan that has its SCM set to use the branch while not using the Plan branching for the release build.

Continuous Integration - SCM Trunk (polling)

( branch) - branch from CI (polling)

Release X - SCM Trunk (dependent on CI)

Release Y – SCM branch (dependent on CI branch)

Can a branch build be used to trigger another plan? If so, how?

Also, can a SVN tag be used as the basis for a Plan branch like an SVN branch can?

[AhmadDanial]

Hey there, Kevin.

I noticed that it has been a while since you receive any response here. Have you raised a ticket in https://support.atlassian.com to seek help from the support engineers regarding the questions that you have here? If no, I would kindly suggest you to do so.

Hope this helps and all the best.