Specify events that trigger pipelines
In Microsoft Team Foundation Server (TFS) 2018 and previous versions, build and release pipelines are called definitions, runs are called builds, service connections are called service endpoints, stages are called environments, and jobs are called phases.
Use triggers to run a pipeline automatically. Azure Pipelines supports many types of triggers. Based on your pipeline's type, select the appropriate trigger from the list below:
Classic build pipelines and YAML pipelines
- CI triggers in Azure Repos Git
- CI triggers in GitHub
- CI triggers in BitBucket Cloud
- CI triggers in TFVC
Gated check-in is supported for TFVC repositories.
Comment triggers are supported only for GitHub repositories.
Scheduled triggers are independent of the repository and allow you to run a pipeline according to a schedule.
Classic release pipelines
Continuous deployment triggers help you start classic releases after a classic build or YAML pipeline completes.
Scheduled release triggers allow you to run a release pipeline according to a schedule.
Pull request release triggers are used to deploy a pull request directly using classic releases.
Stage triggers in classic release are used to configure how each stage in a classic release is triggered.