Jenkins cron expression: every Saturday and Sunday at 10:00 AM

Use H 10 * * 0,6. At a hashed minute (Jenkins picks it from the job name), during hour 10, on Sun and Sat.

To run a Jenkins job every Saturday and Sunday at 10:00 AM, use:

H 10 * * 0,6

At a hashed minute (Jenkins picks it from the job name), during hour 10, on Sun and Sat.

Jenkins (H syntax) expression

Schedule time zone

Your week at a glance

fewer more runs

Upcoming runs

#	Local	UTC	From now

Weekend-only work: batch jobs that should not compete with weekday traffic.

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('H 10 * * 0,6') }
    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.

Sunday is 0 (or 7) in Unix, and 1 in Quartz and EventBridge. Saturday is 6 in Unix but 7 in Quartz.

How do I run a Jenkins job every Saturday and Sunday at 10:00 AM?

Use H 10 * * 0,6. At a hashed minute (Jenkins picks it from the job name), during hour 10, on Sun and Sat.

What is the every Saturday and Sunday at 10:00 AM cron expression in other systems?

Quartz: 0 0 10 ? * 1,7; Spring: 0 0 10 * * 0,6; Crontab: 0 10 * * 0,6. 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.