Jenkins cron expression: once a year on January 1st

Use H 0 1 1 *. At a hashed minute (Jenkins picks it from the job name), during hour 00, on the 1st of the month, in Jan.

To run a Jenkins job once a year on January 1st, use:

H 0 1 1 *

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

Jenkins (H syntax) expression

Schedule time zone

Your week at a glance

fewer more runs

Upcoming runs

#	Local	UTC	From now

Annual rollovers: new-year counters, yearly archives and licence renewals.

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

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.

In Quartz you can add a year field. Without it the schedule repeats every year, which is usually what you want.

How do I run a Jenkins job once a year on January 1st?

Use H 0 1 1 *. At a hashed minute (Jenkins picks it from the job name), during hour 00, on the 1st of the month, in Jan.

What is the once a year on January 1st cron expression in other systems?

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