-
Notifications
You must be signed in to change notification settings - Fork 106
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
Turn anitya cron job to service #668
Comments
just curious: why is it not possible to send mails from cron or because of a failing cron? |
This is probably possible, I just didn't yet look into this option yet. |
Does it make sense to change it to |
No, because the systemd units aren't working in containers and the release-monitoring.org is managed in OpenShift. |
In development environment |
@abitrolly |
Does it provide logs, error counter and error messages? |
The logs will be handled the same way as they are now. Saved to the database. Error counter must be implemented, error messages are saved to every project even now as update log. |
Otherwise the log of the container is accessible in OpenShift, I can look at it there. |
Did you consider celery? |
@TomasTomecek Didn't heard about it. I will give it a try. |
I looked at it and it's not really usable for Anitya. It needs a broker, which is not necessary in our case, because we have all the information internally available in our current database. |
Current cron job used by Anitya is not very reliable.
So it will be better to turn it into service probably using twisted library. This will make scheduling much easier and we could also add the ability to send e-mail when things are failing.
Here is the list of the features it should have:
The text was updated successfully, but these errors were encountered: