May 28, 2014

TFS Build Options Explained: Queue Processing

When creating a new build definition in TFS, one of the first options you're required to select is what type of queue processing you would like the definition to follow. There are three options: Enabled, Paused, and Disabled.

When queue processing is enabled, builds using the definition may be queued by either a manual user action or by an automated trigger (such as a gated check-in or scheduled build). The build controller will then run the builds in order of priority.

When this option is selected, builds can again be queued either manually or automatically. However, the requested builds will sit in the queue until an administrator manually forces them to start. This may be useful when the same build definition is utilized by large, disparate teams and builds are either requested frequently or take a long time to complete.

When queue processing is disabled, the definition can never be used to queue or start a build. Selecting this option prevents triggers such as Continuous Integration or Gated Check-in from being used with the definition. This setting is really only useful as a way to archive a build definition or to prevent its accidental use (perhaps a build administrator would re-enable the definition prior to using it for a Production release).

No comments:

Post a Comment