Home โบ Convert โบ Jenkins to node-cron
Convert Jenkins cron to node-cron
Jenkins expressions look similar to node-cron, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from Jenkins to node-cron
- node-cron has a leading seconds field. The converter adds
0in front so the job fires at the start of the minute. - Jenkins runs when day-of-month or day-of-week matches, but node-cron requires both. If you set both fields, the converter warns you.
- Jenkins
Hvalues pick a per-job offset, which no other system has. The converter replaces them with the start of the range.
Worked examples
| Schedule | Jenkins | node-cron |
|---|---|---|
| every minute | * * * * * | * * * * * |
| every weekday at 8:30 AM | 30 8 * * 1-5 | 30 8 * * 1-5 |
Conversions that come with a warning
- every 5 minutes:
H/5 * * * *โ*/5 * * * *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 10 minutes:
H/10 * * * *โ*/10 * * * *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 15 minutes:
H/15 * * * *โ*/15 * * * *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start. - every 30 minutes:
H/30 * * * *โ*/30 * * * *. Jenkins H values have no equivalent elsewhere; they were replaced by their range start.
Field layout and time zones
minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Jenkins uses the controller's time zone. Put TZ=Asia/Kolkata on its own first line of the trigger to override it.
second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
node-cron uses the server time zone unless you pass { timezone: "Asia/Kolkata" }. Its documentation advises timezone: "UTC" for jobs that must not skip or repeat when clocks change.
Go the other way
Convert node-cron to Jenkins, or open the Jenkins builder or the node-cron builder.
Frequently asked questions
How do I convert a Jenkins cron expression to node-cron?
Paste it into the converter above with Jenkins as the source and node-cron as the target. For example, * * * * * becomes * * * * *.
Is every Jenkins expression convertible to node-cron?
Yes for the common schedules we tested (27 of 27), though unusual expressions with special characters might need manual review.
Does node-cron run in the same time zone as Jenkins?
Not necessarily. Conversion changes the syntax, not the time zone. Check where each system evaluates the schedule before you rely on the same clock times.