BackendBench
Coffee

Home โ€บ Jenkins โ€บ On the last Friday of every month at noon

Jenkins cron

Jenkins cron expression: on the last Friday of every month at noon

To run a Jenkins job on the last Friday of every month at noon, use:

H 12 * * 5

At a hashed minute (Jenkins picks it from the job name), during hour 12, on Fri.

Jenkins cannot express this exactly. The expression above fires more often than you want, so add a guard to the command so it only does the real work on the right day:
H 12 * * 5 [ "$(date -d '+7 days' +\%m)" != "$(date +\%m)" ] && /path/to/job

Your week at a glance
fewer more runs

Upcoming runs

#LocalUTCFrom now

Copy-ready code

Why use this schedule

Month-end releases or reviews that happen on the last Friday. Because months have four or five Fridays, you cannot hard-code a single day number, and each system expresses the rule differently.

First runs, as an example

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

#Date and time (UTC)
1Fri, 01 Jan 2027, 12:00:00
2Fri, 08 Jan 2027, 12:00:00
3Fri, 15 Jan 2027, 12:00:00
4Fri, 22 Jan 2027, 12:00:00
5Fri, 29 Jan 2027, 12:00:00
6Fri, 05 Feb 2027, 12:00:00

On the last Friday of every month at noon in every dialect

SystemExpression
Jenkins (this page)H 12 * * 5
Quartz0 0 12 ? * 6L
Spring0 0 12 * * 5L
Crontab0 12 * * 5
Kubernetes0 12 * * 5
AWS EventBridge0 12 ? * 6L *
GitHub Actions0 12 * * 5
node-cron0 12 * * 5L
Apache Airflow0 12 * * 5
Azure Functions0 0 12 * * 5
Google Cloud Scheduler0 12 * * 5

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.

Declarative pipeline
pipeline {
    agent any
    triggers { cron('H 12 * * 5') }
    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

The common mistake with this schedule

The L suffix is Quartz and Spring only. Quartz counts Friday as 6, so it is 6L, while Spring counts Friday as 5, so it is 5L.

Frequently asked questions

How do I run a Jenkins job on the last Friday of every month at noon?

Use H 12 * * 5. At a hashed minute (Jenkins picks it from the job name), during hour 12, on Fri. This dialect has no native rule for it, so the job must also check the date (see the guard command above).

What is the on the last Friday of every month at noon cron expression in other systems?

Quartz: 0 0 12 ? * 6L; Spring: 0 0 12 * * 5L; Crontab: 0 12 * * 5. 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.

Similar Jenkins schedules

More tools you might need