Jenkins cron expression: every 30 minutes

Use H/30 * * * *. Every 30 minutes (Jenkins picks the offset).

To run a Jenkins job every 30 minutes, use:

H/30 * * * *

Every 30 minutes (Jenkins picks the offset).

Jenkins (H syntax) expression

Schedule time zone

Your week at a glance

fewer more runs

Upcoming runs

#	Local	UTC	From now

Twice an hour, on the hour and half past. Light enough for moderately heavy jobs.

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/30 * * * *') }
    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).

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.
Jenkins uses the controller's time zone. Put TZ=Asia/Kolkata on its own first line of the trigger to override it.

If you want "every half hour starting at :10" you need a list like 10,40, not */30, which always lands on :00 and :30.

How do I run a Jenkins job every 30 minutes?

Use H/30 * * * *. Every 30 minutes (Jenkins picks the offset).

What is the every 30 minutes cron expression in other systems?

Quartz: 0 */30 * * * ?; Spring: 0 */30 * * * *; Crontab: */30 * * * *. 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.