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.


Has anyone figured out a way to do this?



It's not possible to disable run button. We have the related request to prompt for confirmation after Run button is pressed, please vote for it. As current workaround you can add prompt parameter, in this case custom run dialog will be shown if you clicks to 'Run' button.


Please sign in to leave a comment.