CODEWITHSUNDEEP
tfsmsbuildtfsbuild
Dav Evans
Dav Evans

Reputation: 4071

Filter projects which trigger build in tfs

Is there any within team build 2010 (tfs) to decouple the projects found under the build's workspace from the projects which will trigger a build?

I'd like to be able to specify a subset of the projects in my workspace as being those that trigger a build when changed. At the moment any change in the active paths of the workspace will trigger a build.

Upvotes: 0

Views: 719

Answers (3)

pantelif
pantelif

Reputation: 8544

In general, I tend to agree with John Saunders, still:
You can have the projects you wish to not trigger your build in a separate spot within your source control. Remove them from your main solution as projects & add them as assemblies.

This way, any change in your secondary sources will not trigger your main build - merging the compiled assembly will. The gain is that the latter can be done at any time you choose to.

Using file reference has several disadvantages in your case, the main being you can't directly debug the compiled assembly. See also here.

Upvotes: 1

Ludwo
Ludwo

Reputation: 6193

You can create more build definitions to build only specific projects. I had two sets of projects, framework and modules projects. I had two CI build definitions, one for framework set and one for modules. If I changed framework project, framework build was triggered and all output assemblies were checked-in into TFS into BuildAssemblies folder. This folder is included in Modules build definition workspace because BuildAssemblies are referenced from modules projects. Normally if I change BuildAssemblies content modules build should be triggered, but I checked my changes with ***NO_CI*** prefix to not trigger modules build.

But this is not good design. If you change framework assembly and break modules build by this change, you don't know about it until you manually trigger modules build. It makes no sense to use gated check-in feature for modules build.

Upvotes: 1

Duat Le
Duat Le

Reputation: 3596

The only way is to remove those projects from the build definition's workspace mappings. The projects, of course, are still in the branch and your workspace.

Upvotes: 0

Related Questions