Question

I’d prefer to solve this using a Team Build/build definition, but I’m open to other solutions.

Currently, I have a build definition that builds my main branch. If I want to build other branches, what’s the easiest way? Do I have to clone and modify the build definition for each branch, or is there an easier and more elegant way?

(Specifically, the build definition builds MSI files, and I’d love to just one-click to build MSI files for any previous release branch.)

MyCollection
|
|-- MyProject
     |
     |-- MainBranch
     |    |
     |    |-- MySolution.sln
     |
     |-- EarlierReleasesFolder
          |
          |-- ReleaseBranch-2012-01
          |    |
          |    |-- MySolution.sln
          |
          |-- ReleaseBranch-2012-02
          |    |
          |    |-- MySolution.sln
          |
          |-- ReleaseBranch-2012-03
          |    |
          |    |-- MySolution.sln
          |
          |-- ReleaseBranch-2012-04
          |    |
          |    |-- MySolution.sln

Answer 1

Currently, I’m thinking:

• Code against the TFS API to automatically create build
  definitions for each release branch; or:
• Manually create the build definitions (using Power Tools to be able to clone build definitions)