Home โบ Jenkins โบ Every Sunday at midnight
Jenkins cron expression: every Sunday at midnight
To run a Jenkins job every Sunday at midnight, use:
H 0 * * 0At a hashed minute (Jenkins picks it from the job name), during hour 00, on Sun.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
The traditional weekly maintenance slot, at the very start of Sunday. It sits in the quietest part of the week for most business systems, so heavy clean-up jobs rarely disturb anyone.
- Weekly log rotation
- Weekly vacuum or optimise
- Weekly data exports
First runs, as an example
Starting from 1 January 2027, evaluated in UTC (the hashed H offset is shown as its range start):
| # | Date and time (UTC) |
|---|---|
| 1 | Sun, 03 Jan 2027, 00:00:00 |
| 2 | Sun, 10 Jan 2027, 00:00:00 |
| 3 | Sun, 17 Jan 2027, 00:00:00 |
| 4 | Sun, 24 Jan 2027, 00:00:00 |
| 5 | Sun, 31 Jan 2027, 00:00:00 |
| 6 | Sun, 07 Feb 2027, 00:00:00 |
Every Sunday at midnight in every dialect
| System | Expression |
|---|---|
| Jenkins (this page) | H 0 * * 0 |
| Quartz | 0 0 0 ? * 1 |
| Spring | 0 0 0 * * 0 |
| Crontab | 0 0 * * 0 |
| Kubernetes | 0 0 * * 0 |
| AWS EventBridge | 0 0 ? * 1 * |
| GitHub Actions | 0 0 * * 0 |
| node-cron | 0 0 * * 0 |
| Apache Airflow | 0 0 * * 0 |
| Azure Functions | 0 0 0 * * 0 |
| Google Cloud Scheduler | 0 0 * * 0 |
Need to translate a different expression? Use the cron converter.
Ready-to-use Jenkins config
Drop this into your project. The expression is the one above.
pipeline {
agent any
triggers { cron('H 0 * * 0') }
stages {
stage('Build') { steps { echo 'Scheduled build' } }
}
}The Jenkins fields, in order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Things to watch out for in Jenkins
- Day-of-week is 0-7 with Sunday as 0 or 7, as in standard cron.
- Use H instead of a fixed minute to spread load. H 2 * * * means "once during the 2 AM hour", at a stable per-job minute.
- Jenkins uses the controller's time zone. Put TZ=Asia/Kolkata on its own first line of the trigger to override it.
The common mistake with this schedule
Sunday as 0 works in Unix cron but not in Quartz, where the range is 1-7. Use 1 or SUN there.
Frequently asked questions
How do I run a Jenkins job every Sunday at midnight?
Use H 0 * * 0. At a hashed minute (Jenkins picks it from the job name), during hour 00, on Sun.
What is the every Sunday at midnight cron expression in other systems?
Quartz: 0 0 0 ? * 1; Spring: 0 0 0 * * 0; Crontab: 0 0 * * 0. The table on this page lists every dialect.
Which time zone does Jenkins use for this schedule?
Jenkins uses the controller's time zone. Put TZ=Asia/Kolkata on its own first line of the trigger to override it.