BackendBench
Coffee

Home › Convert › Jenkins to Azure Functions

Jenkins → Azure Functions

Convert Jenkins cron to Azure Functions

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

Result

    What changes from Jenkins to Azure Functions

    Worked examples

    ScheduleJenkinsAzure Functions
    every minute* * * * *0 * * * * *
    every weekday at 8:30 AM30 8 * * 1-50 30 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.

    Azure Functions

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

    Azure Functions evaluates NCRONTAB in UTC unless the WEBSITE_TIME_ZONE app setting is set; with it, the schedule adjusts for daylight saving. The setting is not supported on Linux Consumption or Flex Consumption plans.

    Go the other way

    Convert Azure Functions to Jenkins, or open the Jenkins builder or the Azure Functions builder.

    Frequently asked questions

    How do I convert a Jenkins cron expression to Azure Functions?

    Paste it into the converter above with Jenkins as the source and Azure Functions as the target. For example, * * * * * becomes 0 * * * * *.

    Is every Jenkins expression convertible to Azure Functions?

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

    Does Azure Functions 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