You can change the advanced configuration options for your build definition. These options include a description, the format of the build number, and the automated creation of work items on failures and times. To set this up, go through the following steps:

1. Click on the Options tab. You should arrive at the following screen:

2. Now, create your build number format. If this field is left empty, then the build number for your application will be set to an ever-increasing number that will increase by 1 with every build. This number is unique within a team project and counts over all the build definitions. You can also specify a format of your own using the variables available to you. A common approach is to specify a major and minor version number manually and then add an increasing number using a variable. The following example specifies a version of 4.1.xx, where the last part is replaced by a two-digit increasing number:

4.1($Rev:.rr)

3. On the right, there are advanced (but rarely used) options for specifying the authorization scope for the Build job time-outs for each job in the build definition.
4. It is also possible to specify the agent demands that every agent, for every job in the build definition, should fulfill. Again, we will look further at demands in the Agents and agent queues section of this chapter.

Other options on the left enable you to suspend the pipeline temporarily.