Home › Convert › GitHub Actions to Jenkins
Convert GitHub Actions cron to Jenkins
GitHub Actions expressions look similar to Jenkins, but the differences matter. Paste yours below; the result is checked against the original run times.
What changes from GitHub Actions to Jenkins
- Jenkins
His optional, but using it (for exampleH/15instead of*/15) spreads load across your jobs.
Worked examples
| Schedule | GitHub Actions | Jenkins |
|---|---|---|
| every 5 minutes | */5 * * * * | */5 * * * * |
| every 10 minutes | */10 * * * * | */10 * * * * |
| every 15 minutes | */15 * * * * | */15 * * * * |
| every 30 minutes | */30 * * * * | */30 * * * * |
| every hour | 0 * * * * | 0 * * * * |
| every 2 hours | 0 */2 * * * | 0 */2 * * * |
| every 3 hours | 0 */3 * * * | 0 */3 * * * |
| every 6 hours | 0 */6 * * * | 0 */6 * * * |
Field layout and time zones
minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).
GitHub Actions schedules are always UTC. Convert your local time to UTC before writing the expression.
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.
Go the other way
Convert Jenkins to GitHub Actions, or open the GitHub Actions builder or the Jenkins builder.
Frequently asked questions
How do I convert a GitHub Actions cron expression to Jenkins?
Paste it into the converter above with GitHub Actions as the source and Jenkins as the target. For example, */5 * * * * becomes */5 * * * *.
Is every GitHub Actions expression convertible to Jenkins?
Yes for the common schedules we tested (26 of 26), though unusual expressions with special characters might need manual review.
Does Jenkins run in the same time zone as GitHub Actions?
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.