Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow cronjobs to be executed by calling the built binary #71

Open
wilzbach opened this issue Mar 30, 2017 · 4 comments
Open

Allow cronjobs to be executed by calling the built binary #71

wilzbach opened this issue Mar 30, 2017 · 4 comments
Labels

Comments

@wilzbach
Copy link
Member

@MartinNowak
Copy link
Member

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
Copy link
Member Author

wilzbach commented Jan 15, 2018

Currently the cron runs every six hours:

image

@wilzbach 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
@CyberShadow
Copy link
Member

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.

@CyberShadow
Copy link
Member

I got it working again, though, it seems to take a very long time to run.

Figured it out, it was getting stuck in an infinite loop because it wasn't parsing the "Link" header properly:
CyberShadow@01ebb41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants