Home › Jenkins › Every hour

At a hashed minute (Jenkins picks it from the job name).

Why use this schedule

One run at the top of each hour, twenty-four a day. This is the classic maintenance cadence: frequent enough to keep data fresh, slow enough that even a heavier job finishes comfortably before the next one starts.

• Rotating or compressing logs
• Hourly aggregation of events
• Refreshing materialised views

First runs, as an example

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

Every hour in every dialect

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

• 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

Many teams start everything at minute 0, which creates a thundering herd on shared systems. Offset heavy jobs, for example to minute 7 or 23, or use H in Jenkins.

Similar Jenkins schedules