Home/ Questions/Q 103737
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T01:10:16+00:00

If you follow some of MS’s recommended branching strategies you can easily end up

  • 0

If you follow some of MS’s recommended branching strategies you can easily end up with a project structure such as:

$PROJECT\     DEV\         MyProject     STAGE\         MyProject     PROD\         MyProject

Now let’s say I have three different build definitions. One each for DEV, STAGE, and PROD. This should be common considering that the build definition will define the exact solutions to build.

If I turn on CI for each of them, STAGE will be built even though the checkin occurred in DEV…

Now my question. How can I limit the build definition to execute only when a check in occurs in either a path or a solution that is part of the build definition?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. When defining the working folder configuration screen – only have it start at the root of the branch you want to build.

    For example, your DEV branch would be configured so that $/TEAMPROJECT/DEV/MyProject was mapped to $(SourceDir) rather than the default mapping which would have been set to just $/TEAMROJECT.

    FYI – Personally, I only have CI Builds on Dev branches and queue manual builds for a push to QA. I also normally don’t do a re-build for production but just push the build binaries that were QA’d. I also keep by build configuration folder inside the branch i.e. $/TEAMPROJECT/DEV/TeamBuild rather than the default $/TEAMPROJECT/TeamBuildTypes and therefore changes to the build configuration are also pushed up through the branches. That said, you have to stick with the default if you wanted the build configuration to be visible to VS2005 clients.

    Hope that helps,

    Martin.

    • 0