Events
17 Mar, 21 - 21 Mar, 10
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowClassic pipelines configuration
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
Classic pipelines make it easier for developers to design their pipeline workflows using the user interface to add tasks and conditions tailored to their scenario. This article explains the available options to configure your agent job and explores the different build properties for your Classic pipeline.
Sign in to your Azure DevOps organization, and then go to your project.
Select Pipelines, select your pipeline definition, and then select Edit.
Select Tasks, and then select Agent job.
When you queue a build, it runs on an agent from your selected pool. You can choose a Microsoft-hosted pool or a self-hosted pool that you manage. Select the pool associated with the agents you want to run this pipeline on.
Defines how the job's tasks are executed in parallel:
None: tasks are executed on a single agent.
Multi-configuration: tasks are executed on multiple configurations, as specified in the multipliers. Configurations run in parallel, each using a single agent. The total number of agents depends on the number of configurations and can be limited by setting a maximum number of agents.
Multi-agent: tasks are executed on multiple agents using the specified number of agents.
Specifies the maximum time, in minutes, that a deployment is allowed to run on an agent before being canceled by the server. The duration is measured after preapproval is completed and before post-approval is requested. A value of zero will cause the timeout of the parent pipeline to be used.
Specifies the maximum wait time for a deployment job to respond to a cancellation request before being terminated by the server. A value of zero will cause the timeout of the parent pipeline to be used.
Enables scripts and other processes to access the OAuth token through the System.AccessToken variable. See the example script for accessing the REST API for more details.
Sign in to your Azure DevOps organization, and then go to your project.
Select Pipelines, select your pipeline definition, select Edit, and then select the Options tab.
Define the format to give meaningful names to completed builds. Leave it blank to give builds a unique integer as name. See Configure build run numbers for more details.
When enabled, if the pipeline fails, a work item is automatically created to track the issue. You can specify the type of work item and choose whether to assign it to the requestor.
- Additional Fields: set additional fields when creating the work item.
For example, "System.Title" = "Build $(build.buildNumber) failed" formats the Work Item title, and "System.Reason" = "Build failure" sets the reason. See Work item field index for other available fields.
Define build job authorization and timeout settings.
Build job authorization scope: specify the authorization scope for a build job. Select:
- Project Collection: if the pipeline needs access to multiple projects.
- Current Project: if you want to restrict this pipeline to only access the resources in the current project.
See Understand job access tokens for more details.
Build job timeout in minutes: specifies the maximum time a build job is allowed to execute on an agent before being canceled by the server. An empty or zero value indicates no timeout limit.
Build job cancel timeout in minutes: specifies the maximum wait time for a build job to respond to a cancellation request before being terminated by the server.
Specify the capabilities that the agent must have to run this pipeline. See Agent capabilities and demands for more details.
