You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's a weird cron, but workable. How often do we get migrated on Heroku? You could always run on full hours if you happen to be on at that time.
Also an anacron approach would work but requires some state.
wilzbach
changed the title
Allow cronjobs to be executed by the calling the built binary
Allow cronjobs to be executed by calling the built binary
Feb 19, 2019
So as discussed on Slack, this seems to have fallen off at some point.
I got it working again, though, it seems to take a very long time to run. Even with Vibe.d connection persistence fixed, it's been running for three hours and hasn't even finished going through the DMD pull requests. This may need some adjustments going forward.
--run
https://devcenter.heroku.com/articles/scheduler
The text was updated successfully, but these errors were encountered: