Specify events that trigger pipelines

CI triggers run a pipeline when a push is made to a branch that meets the criteria defined by the trigger. Use the trigger keyword to configure a CI trigger. For example, to run a pipeline when a push is made to the main branch, specify the following trigger.

trigger:
- main

To disable CI triggers in your pipeline, use the following syntax.

trigger: none

YAML pipelines support CI triggers for the following repository types. For specific information about using CI triggers with a specific repository type, see the following articles.

• CI triggers in Azure Repos Git
• CI triggers in GitHub
• CI triggers in GitHub Enterprise Server
• CI triggers in Bitbucket Cloud

For information on the full YAML trigger syntax and options available for CI triggers, see trigger definition.

CI triggers run a pipeline when a push is made to a branch that meets the criteria defined by the trigger.

For more information about using CI triggers with a specific repository type, see the following articles.

• CI triggers in Azure Repos Git
• CI triggers in GitHub
• CI triggers in Bitbucket Cloud
• CI triggers in TFVC

Classic build pipelines support CI triggers for GitHub Enterprise Server, Bitbucket Server, and Subversion repositories if Azure Pipelines can access the repositories.

Pull request (PR) triggers cause a pipeline to run whenever you open a pull request, or when you push changes to the source branch of a pull request. Use the pr keyword to configure a PR trigger. For example, to run a pipeline when a PR is raised to the main branch, specify the following trigger.

pr:
- main

If you don't explicitly configure PR triggers in your pipeline, they're enabled by default, unless UI settings override YAML trigger. Pull requests to any branch trigger a pipeline run. To disable PR triggers in your pipeline, use the following syntax.

pr: none

YAML PR triggers are supported for GitHub and Bitbucket Cloud. For more information about using PR triggers with these types of repositories, see PR triggers in GitHub and PR triggers in Bitbucket Cloud. For information on the full YAML PR trigger syntax, see pr definition.

Azure Repos Git uses branch policies to implement PR triggers. For more information, see PR triggers in Azure Repos Git.

Pull request (PR) triggers cause a pipeline to run whenever you open a pull request, or when you push changes to the source branch of an existing pull request.

PR triggers are supported for GitHub and Bitbucket Cloud. For more information about using PR triggers with these types of repositories, see PR triggers in GitHub and PR triggers in Bitbucket Cloud.

Azure Repos Git uses branch policies to implement PR triggers. For more information, see PR triggers in Azure Repos Git.

TFVC repositories don't have pull requests or pull request triggers, but do support gated check-in.

Scheduled triggers run a pipeline on a predefined schedule. All repository types that support YAML pipelines support scheduled triggers in YAML pipelines. These repository types include Azure Repos Git, GitHub, GitHub Enterprise Server, and Bitbucket Cloud.

To define a scheduled trigger in YAML, use the schedules keyword and define your schedule by using cron syntax. The following example configures a schedule that runs every day at midnight.

# YAML file in the main branch
schedules:
- cron: '0 0 * * *'
  displayName: Daily midnight build
  branches:
    include:
    - main

For more information and examples, see Scheduled triggers, schedules definition, and schedules.cron definition.

Scheduled triggers run a pipeline on a predefined schedule. All repository types supported by Azure DevOps support scheduled triggers. For information and examples, see Scheduled triggers.

Set up a pipeline resource trigger in your pipeline to start a pipeline run when the source pipeline finishes a run.

resources:
  pipelines:
  - pipeline: sourcePipelineResource # Label for this pipeline resource; used when referring to it elsewhere in the pipeline.
    source: source-pipeline # The name of the pipeline referenced by this pipeline resource.
    project: FabrikamProject # Required only if the source pipeline is in another project
    trigger: true # Run this pipeline when any run of source-pipeline completes

You can add multiple pipeline resources in your pipeline. You can configure the trigger to run when any version of the source pipeline finishes, or limit it to certain branches.

For more information and examples, see Pipeline completion triggers.

For the full syntax and trigger options, see resources.pipelines.pipeline definition.

Set up build completion triggers in the classic designer to run your pipeline when another pipeline in the same project finishes. You can optionally download artifacts from the completed run. For more information, see Build completion triggers (classic).