ENH: Test should run regularly from cron #147
Conversation
There was a problem hiding this comment.
Thanks @bsipocz , this is definitely something we want to do.
One thing I'd like to figure out is what to do when a scheduled job fails. AIUI, if a scheduled job failed at this point, you (and only you) would get an email since you were the last person to touch the cron syntax.
IMO the nicest solution would be to automatically generate an issue when a scheduled job fails; that way everyone who is watching the repo would be notified. Other solutions might be to a) add more devs to the notifications list and/or b) add a status badge to the readme.
I definitely prefer the auto-issue solution, though I don't know exactly how to implement it (maybe this action is a good place to start?). Of course, we don't have to figure this out right now - I'm happy to merge if you don't mind being the point-of-contact for failing scheduled jobs for a bit - just LMK!
Thanks for digging that info up, I was puzzled at another repo where I'm admin, yet never received the cron notifications. |
|
I can try and look into the auto issue opening, but also I'm totally fine being the one getting the default notifications in the meantime. basically, my gh notifications inbox is the only one I reasonably manage as zero inbox, so will certainly notice and can open an issue manually if needed. |
Great! Let's get this in then and figure out the notifications piece in a follow-up. Thanks @bsipocz ! |
This does the bare minimum of enabling cron testing, and I don't think will be controversial. It maybe optimized later to cut back on the number of jobs being run (but maybe that's better done after/in #146 when e.g. developer and/or pre-release version of dependencies are added, etc.)