Build definition options

Last Update: 3/6/2017

Team Services | TFS 2017 | TFS 2015 | Previous versions (XAML builds)

Here we explain settings you can change on the build definition Options tab.

MultiConfiguration

Select this option to build multiple configurations. For example, you could build a C++ app for both debug and release configurations on both x86 and x64 platforms. For details about this example, see Visual Studio Build.

Create a work item on failure

If the build process fails, you can automatically create a work item to track getting the problem fixed. You can specify the work item type.

You can also select if you want to assign the work item to the requestor. For example, if this is a CI build, and a team member checks in some code that breaks the build, then the work item is assigned to that person.

Additional Fields: You can set the value of work item fields. For example:

Field Value
System.Title Build $(Build.BuildNumber) failed
System.Reason Build failure

Q: What other work item fields can I set? A: Work item field index

Allow scripts to access the OAuth token

Select this check box if you want to enable your script to use the build process OAuth token.

For an example, see Use a script to customize your build process.

Q&A

Do I need a build agent?

You need at least one agent to run your build. Get an agent.

I can't select a default agent queue and I can't queue my build. How do I fix this?

See queues.

I use Team Foundation Server on-premises and I don't see some of these features. Why not?

Some of these features are available only on Visual Studio Team Services and not yet available on-premises. Some features are available on-premises if you have upgraded to the latest version of TFS.