Restricting build configurations to only run on promotion


We have several projects setup the following way:

1. Build config 1:  compile and run unit tests + deploy to integration environments - automatically triggered on VCS changes
2. Build config 2: depends on build config 1.  compile same changeset as build config 1 and deploy to QA environment - no trigger

What we would really like is for build config 2 to only run when promoted from a successful build of build config 1.  So, in other words, we would like for the "run" button on build config 2 to be disabled.  This is to ensure that we only promote specific changesets to QA.  

Is there a way to do this in TC 7.1.3?  Any help would be greatly appreciated.


Please sign in to leave a comment.