Jobs migration from Heroku

Hi,

We’re moving our Phoenix app from Heroku to Render. We have > 20 different jobs running throughout the day (once an hour, once a day, etc).

They all share the same codebase.

If I understand the docs correctly, for each new commit on master, Render builds 20 different new versions, one for each cron job?

Also what happens when a job is running and a new commit is pushed?

Thanks,

1 Like

If I understand the docs correctly, for each new commit on master, Render builds 20 different new versions, one for each cron job?

Can you link to the section of our docs you’re referencing? Each new commit should be one new version of your app, and should include anything within your app infrastructure such as cronjobs.

I’d expect the new commit to immediately start a new deploy of your app in Render, regardless of what your app is currently doing, but will confirm with our team.

Thanks for your answer Aaron.

Here’s the section I’m referencing:

For example, if I create 20 cron jobs from the same GitHub repo and there’s a new commit on this repo. This will trigger 20 distinct builds, correct ?

What we’d love to have is a single build shared by all cron jobs, as there are all from the same repo.

Hope this helps.

1 Like

Thanks for clarifying that part. As for your first question, the executing cron job will continue while the new code is being pushed to the service

If you have 20 cron jobs that are attached to the same repo, a single push to your repo would trigger just one new build in Render. That build would not automatically kick off all 20 cron jobs, they will only run on their scheduled run times. When they do run on schedule, they will have the newest instance of your repo’s code available. Their schedule would not be interrupted by a push to your repo, even if they all use the same repo. Does that help?