Home › Jenkins › On the first day of every quarter

At a hashed minute (Jenkins picks it from the job name), during hour 00, on the 1st of the month, in Jan, Apr, Jul and Oct.

Why use this schedule

January, April, July and October: quarterly reporting and reviews. Finance and compliance teams in particular run on this rhythm, so these jobs tend to be important and rarely run.

• Quarterly business reviews
• Quarterly access recertification
• Quarterly invoices

First runs, as an example

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

On the first day of every quarter 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 0 1 1,4,7,10 *') }
    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

• If you set both day-of-month and day-of-week, Jenkins runs when either matches.
• 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

There is no */3 shortcut that starts in January. */3 in the month field gives 1,4,7,10 in Unix cron, but an explicit list is clearer and safer across dialects.

Similar Jenkins schedules