Build schedules automatically create builds at specified intervals. For example, you can use scheduled builds to run nightly builds, hourly integration tests, or daily ops tasks.
You can create and manage schedules in the Schedules section of your Pipeline Settings.
You can also create and manage schedules via the Buildkite GraphQL API.
The interval defines when the schedule will create builds. Schedules run in UTC time by default, and can be defined using either predefined intervals or standard crontab time syntax.
Buildkite doesn't support intervals less than 10 minutes.
Buildkite supports 6 predefined intervals:
||At the start of every hour||
||Every day at midnight UTC||
||Every week at midnight Sunday UTC||
||Every month, at midnight UTC on the first day||
||Every year, at midnight UTC on the first day||
Crontab time syntax
Intervals can be defined using a variant of the crontab time syntax:
┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday) │ │ │ │ │ ┌─── time zone name or offset (optional) │ │ │ │ │ │ * * * * * Australia/Melbourne
A time zone can optionally be specified as the last segment, either as an IANA Time Zone name like
Europe/Berlin, or as an offset from UTC like
-05:00. If no time zone is given, the schedule will run in UTC.
Buildkite supports several extensions to the standard POSIX cron syntax.
The slash operator allows you to specify step values within ranges. For example,
*/10 * * * * would run every ten minutes.
last in the day of month field represents the last day. For example,
0 0 L * * represents midnight on the last day of the month, and
0 0 -2-L * * represents the last two days of the month.
Using the modulo extension allows you to create schedules for less common sets of weekdays.
Modulo can only be used with the 'day of week' field. For example, 0 0 * * 0 represents midnight on every Sunday. Adding a modulo of 3 creates a schedule that runs at midnight on every third Sunday: 0 0 * * 0%3.
You can also use the offset + operator alongside a modulo value. For instance, adding an offset of 1 to our previous example 0 0 * * 0%3+1 will create a schedule to run a build every third Sunday that is an odd calendar number. Modulo is calculated based on the time since 2019-01-01.
For more information on how modulo works, see the official documentation of Fugit, which is used for extending the POSIX cron syntax in Buildkite.
||Every 10 minutes|
||Every 30 minutes|
||Every 30th minute of every hour|
||Every 4 hours|
||Every 12 hours|
||Every other day at midnight UTC+1|
||Every day at 8am UTC|
||Every day at 8am in Vancouver|
||Every Sunday at 4pm UTC|
||Every weekday at midnight UTC|
||Midnight UTC on the last day of the month|
||Every other month, at midnight UTC on the first day|
||The last day of the month at 4pm UTC|
||The start of every odd Tuesday|