BackendBench
Coffee

Home › Convert › Jenkins to Apache Airflow

Jenkins → Apache Airflow

Convert Jenkins cron to Apache Airflow

Jenkins expressions look similar to Apache Airflow, but the differences matter. Paste yours below; the result is checked against the original run times.

Result

    What changes from Jenkins to Apache Airflow

    Worked examples

    ScheduleJenkinsApache Airflow
    every minute* * * * ** * * * *
    every weekday at 8:30 AM30 8 * * 1-530 8 * * 1-5

    Conversions that come with a warning

    Field layout and time zones

    Jenkins

    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.

    Apache Airflow

    minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).

    Airflow defaults to UTC. On a time-zone-aware DAG a cron schedule follows wall-clock time, so a daily 00:00 US/Eastern run moves between 04:00 and 05:00 UTC across daylight saving changes.

    Go the other way

    Convert Apache Airflow to Jenkins, or open the Jenkins builder or the Apache Airflow builder.

    Frequently asked questions

    How do I convert a Jenkins cron expression to Apache Airflow?

    Paste it into the converter above with Jenkins as the source and Apache Airflow as the target. For example, * * * * * becomes * * * * *.

    Is every Jenkins expression convertible to Apache Airflow?

    Yes for the common schedules we tested (27 of 27), though unusual expressions with special characters might need manual review.

    Does Apache Airflow 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.

    More tools you might need