MN VSTS User Group

Minnesota Visual Studio Team System User Group
Welcome to MN VSTS User Group Sign in | Join | Help
in Search
Sponsored by...

Continuous Integration (multiple builds, same workspace)

Last post 04-07-2008, 7:25 PM by joshua.ewer. 0 replies.
Sort Posts: Previous Next
  •  04-07-2008, 7:25 PM 71

    Continuous Integration (multiple builds, same workspace)

    So, let's say I have two build definitions, ClientDev1 and ClientDevDeploy1.  One build to do the compilation, the second to do all the signing, ClickOnce deployment fun.  They're broken out because I quite often want to just do a build, but not actually deploy.  Then, I can have a ClientTestDeploy, ClientProdDeploy push all the same bits out to other environments.

    If I want TFS 2008 to trigger both builds on a check-in (for instance, they both have a workspace mapped to the same solution), is there any way to explicitly order builds that are triggered from the same check-in?  It seems like if there are several builds triggered at the same time, they just build in alphabetical order?  Any out-of-the-box way to set up dependencies between builds (if BuildA, BuildB and BuildC are all queued at the same time, execute them in this order - ACB)?

    Or, maybe easier, is there an easy way to call one build from another without having to call some external batch file?

View as RSS news feed in XML
Powered by Community Server, by Telligent Systems