Home › Jenkins › On the 15th of every month at midnight

At a hashed minute (Jenkins picks it from the job name), during hour 00, on the 15th of the month.

Why use this schedule

Mid-month jobs, such as payroll runs or the second half of a twice-monthly billing cycle. Paired with the 1st of the month it splits a month into two even halves.

• Mid-month payroll
• Twice-monthly reports (with the 1st)
• Mid-cycle reminders

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 15th of every month at midnight 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 15 * *') }
    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

The 15th can be a weekend. Cron cannot shift to the next business day on its own; check in the job, or use Quartz 15W for the nearest weekday.

Similar Jenkins schedules