Home โบ Jenkins โบ Every Monday at 9:00 AM
Jenkins cron expression: every Monday at 9:00 AM
To run a Jenkins job every Monday at 9:00 AM, use:
H 9 * * 1At a hashed minute (Jenkins picks it from the job name), during hour 09, on Mon.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
A weekly start-of-week job that fires every Monday morning. Teams use it to open the week with a fresh report, a reset counter, or a reminder that lands before the first meeting.
- Weekly team report
- Weekly KPI emails
- Starting a weekly release train
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 | Mon, 04 Jan 2027, 09:00:00 |
| 2 | Mon, 11 Jan 2027, 09:00:00 |
| 3 | Mon, 18 Jan 2027, 09:00:00 |
| 4 | Mon, 25 Jan 2027, 09:00:00 |
| 5 | Mon, 01 Feb 2027, 09:00:00 |
| 6 | Mon, 08 Feb 2027, 09:00:00 |
Every Monday at 9:00 AM in every dialect
| System | Expression |
|---|---|
| Jenkins (this page) | H 9 * * 1 |
| Quartz | 0 0 9 ? * 2 |
| Spring | 0 0 9 * * 1 |
| Crontab | 0 9 * * 1 |
| Kubernetes | 0 9 * * 1 |
| AWS EventBridge | 0 9 ? * 2 * |
| GitHub Actions | 0 9 * * 1 |
| node-cron | 0 9 * * 1 |
| Apache Airflow | 0 9 * * 1 |
| Azure Functions | 0 0 9 * * 1 |
| Google Cloud Scheduler | 0 9 * * 1 |
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 9 * * 1') }
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
In Quartz and EventBridge, 1 means Sunday, so 0 9 ? * 1 fires on Sunday. Monday is 2, or write MON.
Frequently asked questions
How do I run a Jenkins job every Monday at 9:00 AM?
Use H 9 * * 1. At a hashed minute (Jenkins picks it from the job name), during hour 09, on Mon.
What is the every Monday at 9:00 AM cron expression in other systems?
Quartz: 0 0 9 ? * 2; Spring: 0 0 9 * * 1; Crontab: 0 9 * * 1. 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.