Home โบ Jenkins โบ Every 15 minutes during business hours on weekdays
Jenkins cron expression: every 15 minutes during business hours on weekdays
To run a Jenkins job every 15 minutes during business hours on weekdays, use:
H/15 9-17 * * 1-5Every 15 minutes (Jenkins picks the offset), during hours 09, 10, 11, 12, 13, 14, 15, 16, 17, on Mon, Tue, Wed, Thu and Fri.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Frequent checks during working hours only, which cuts the number of runs by about two thirds compared with all day, every day.
- Order-desk polling
- Intraday risk or trade reports
- Helpdesk escalation checks
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, 09:00:00 |
| 2 | Fri, 01 Jan 2027, 09:15:00 |
| 3 | Fri, 01 Jan 2027, 09:30:00 |
| 4 | Fri, 01 Jan 2027, 09:45:00 |
| 5 | Fri, 01 Jan 2027, 10:00:00 |
| 6 | Fri, 01 Jan 2027, 10:15:00 |
Every 15 minutes during business hours on weekdays in every dialect
| System | Expression |
|---|---|
| Jenkins (this page) | H/15 9-17 * * 1-5 |
| Quartz | 0 */15 9-17 ? * 2-6 |
| Spring | 0 */15 9-17 * * 1-5 |
| Crontab | */15 9-17 * * 1-5 |
| Kubernetes | */15 9-17 * * 1-5 |
| AWS EventBridge | */15 9-17 ? * 2-6 * |
| GitHub Actions | */15 9-17 * * 1-5 |
| node-cron | */15 9-17 * * 1-5 |
| Apache Airflow | */15 9-17 * * 1-5 |
| Azure Functions | 0 */15 9-17 * * 1-5 |
| Google Cloud Scheduler | */15 9-17 * * 1-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/15 9-17 * * 1-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
- H/15 starts every 15 minutes at a hashed offset per job, which avoids every job firing at :00. The preview here assumes an offset of 0.
- Day-of-week is 0-7 with Sunday as 0 or 7, as in standard cron.
- 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 last run is 17:45, not 17:00, because the hour range is 9-17 and the minute step still fires inside hour 17.
Frequently asked questions
How do I run a Jenkins job every 15 minutes during business hours on weekdays?
Use H/15 9-17 * * 1-5. Every 15 minutes (Jenkins picks the offset), during hours 09, 10, 11, 12, 13, 14, 15, 16, 17, on Mon, Tue, Wed, Thu and Fri.
What is the every 15 minutes during business hours on weekdays cron expression in other systems?
Quartz: 0 */15 9-17 ? * 2-6; Spring: 0 */15 9-17 * * 1-5; Crontab: */15 9-17 * * 1-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.