Home โบ Jenkins โบ On the 1st of every month at midnight
Jenkins cron expression: on the 1st of every month at midnight
To run a Jenkins job on the 1st of every month at midnight, use:
H 0 1 * *At a hashed minute (Jenkins picks it from the job name), during hour 00, on the 1st of the month.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Monthly jobs that start with the calendar month: billing runs, quota resets, monthly reports.
- Monthly billing and invoices
- Resetting monthly usage quotas
- Previous-month reports
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 | Fri, 01 Jan 2027, 00:00:00 |
| 2 | Mon, 01 Feb 2027, 00:00:00 |
| 3 | Mon, 01 Mar 2027, 00:00:00 |
| 4 | Thu, 01 Apr 2027, 00:00:00 |
| 5 | Sat, 01 May 2027, 00:00:00 |
| 6 | Tue, 01 Jun 2027, 00:00:00 |
On the 1st of every month at midnight in every dialect
| System | Expression |
|---|---|
| Jenkins (this page) | H 0 1 * * |
| Quartz | 0 0 0 1 * ? |
| Spring | 0 0 0 1 * * |
| Crontab | 0 0 1 * * |
| Kubernetes | 0 0 1 * * |
| AWS EventBridge | 0 0 1 * ? * |
| GitHub Actions | 0 0 1 * * |
| node-cron | 0 0 1 * * |
| Apache Airflow | 0 0 1 * * |
| Azure Functions | 0 0 0 1 * * |
| Google Cloud Scheduler | 0 0 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 0 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
- If you set both day-of-month and day-of-week, Jenkins runs when either matches.
- 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
The month field is 1-12 (January is 1), and the day-of-month field starts at 1, not 0.
Frequently asked questions
How do I run a Jenkins job on the 1st of every month at midnight?
Use H 0 1 * *. At a hashed minute (Jenkins picks it from the job name), during hour 00, on the 1st of the month.
What is the on the 1st of every month at midnight cron expression in other systems?
Quartz: 0 0 0 1 * ?; Spring: 0 0 0 1 * *; Crontab: 0 0 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.