| title | description | ms.date | monikerRange |
|---|---|---|---|
schedules definition |
The schedules list specifies the scheduled triggers for the pipeline. |
11/12/2024 |
>=azure-pipelines-2020 |
:::moniker range=">=azure-pipelines-2020"
The schedules list specifies the scheduled triggers for the pipeline.
:::moniker-end
:::moniker range=">=azure-pipelines-2020"
schedules: [ cron ] # The schedules list specifies the scheduled triggers for the pipeline.:::moniker-end
:::moniker range=">=azure-pipelines-2020"
Definitions that reference this definition: pipeline
:::moniker-end
:::moniker range=">=azure-pipelines-2020"
| Type | Description |
|---|---|
| schedules.cron | A scheduled trigger specifies a schedule on which branches are built. |
:::moniker-end
If you specify no scheduled trigger, no scheduled builds occur.
Important
Scheduled triggers defined using the pipeline settings UI take precedence over YAML scheduled triggers.
If your YAML pipeline has both YAML scheduled triggers and UI defined scheduled triggers, only the UI defined scheduled triggers are run. To run the YAML defined scheduled triggers in your YAML pipeline, you must remove the scheduled triggers defined in the pipeline settings UI. Once all UI scheduled triggers are removed, a push must be made in order for the YAML scheduled triggers to start being evaluated.
To delete UI scheduled triggers from a YAML pipeline, see UI settings override YAML scheduled triggers.
- schedules.cron
- Learn more about scheduled triggers.
- Learn more about triggers in general and how to specify them.