Jenkins cron expression: every weekday at 8:30 AM

Use 30 8 * * 1-5. At 08:30 UTC, on Mon, Tue, Wed, Thu and Fri.

To run a Jenkins job every weekday at 8:30 AM, use:

30 8 * * 1-5

At 08:30 UTC, on Mon, Tue, Wed, Thu and Fri.

Jenkins (H syntax) expression

Schedule time zone

Your week at a glance

fewer more runs

Upcoming runs

#	Local	UTC	From now

A half-hour offset before the working day starts, so output is waiting by 9.

Starting from 1 January 2027, evaluated in UTC (the hashed H offset is shown as its range start):

Need to translate a different expression? Use the cron converter.

Drop this into your project. The expression is the one above.

Declarative pipeline

pipeline {
    agent any
    triggers { cron('30 8 * * 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).

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 minute comes first, then the hour. 30 8 means 08:30, while 8 30 would be an invalid hour.

How do I run a Jenkins job every weekday at 8:30 AM?

Use 30 8 * * 1-5. At 08:30 UTC, on Mon, Tue, Wed, Thu and Fri.

What is the every weekday at 8:30 AM cron expression in other systems?

Quartz: 0 30 8 ? * 2-6; Spring: 0 30 8 * * 1-5; Crontab: 30 8 * * 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.