Home โบ Jenkins โบ Every Friday at 5:00 PM
Jenkins cron expression: every Friday at 5:00 PM
To run a Jenkins job every Friday at 5:00 PM, use:
H 17 * * 5At a hashed minute (Jenkins picks it from the job name), during hour 17, on Fri.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
An end-of-week run on Friday evening. It closes out the working week, which makes it a natural time for weekly invoices, summaries, and backups before the quiet weekend hours.
- Weekly invoicing
- End-of-week summaries
- Pre-weekend backups
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, 17:00:00 |
| 2 | Fri, 08 Jan 2027, 17:00:00 |
| 3 | Fri, 15 Jan 2027, 17:00:00 |
| 4 | Fri, 22 Jan 2027, 17:00:00 |
| 5 | Fri, 29 Jan 2027, 17:00:00 |
| 6 | Fri, 05 Feb 2027, 17:00:00 |
Every Friday at 5:00 PM in every dialect
| System | Expression |
|---|---|
| Jenkins (this page) | H 17 * * 5 |
| Quartz | 0 0 17 ? * 6 |
| Spring | 0 0 17 * * 5 |
| Crontab | 0 17 * * 5 |
| Kubernetes | 0 17 * * 5 |
| AWS EventBridge | 0 17 ? * 6 * |
| GitHub Actions | 0 17 * * 5 |
| node-cron | 0 17 * * 5 |
| Apache Airflow | 0 17 * * 5 |
| Azure Functions | 0 0 17 * * 5 |
| Google Cloud Scheduler | 0 17 * * 5 |
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 17 * * 5') }
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
Friday is 5 in Unix and 6 in Quartz. A direct copy between them shifts the job by a day.
Frequently asked questions
How do I run a Jenkins job every Friday at 5:00 PM?
Use H 17 * * 5. At a hashed minute (Jenkins picks it from the job name), during hour 17, on Fri.
What is the every Friday at 5:00 PM cron expression in other systems?
Quartz: 0 0 17 ? * 6; Spring: 0 0 17 * * 5; Crontab: 0 17 * * 5. 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.