summaryrefslogtreecommitdiff
path: root/jobmanager.py
Commit message (Collapse)AuthorAgeFilesLines
* env python -> python3Tom Ritter2020-09-071-1/+1
|
* Run futurize on the codebase for python3Tom Ritter2020-09-071-1/+3
|
* Fix executions that stomped on each otherTom Ritter2017-11-111-2/+2
| | | | | | | | | | | | Every hour I would fire off two executions: the minute execution and the hour execution. Each would read the statefile on start. Whichever execution took longer would overwrite the state file with the data that was present for the other's execution upon start. This would manifest as extra notifications if the starts aligned - because the 'I already sent a notification' member update wasn't being persisted. This fixes it by only performing one execution at any given time, but knowing to run all the relevant jobs for that type of execution. AKA When I run the hourly job I also run the minute jobs. Another problem related to this one is logged in #1 - minute executions that take longer than a minute will also cause this type of error.
* Hopefully finally solve the bug about only getting success messages for ↵Tom Ritter2017-03-031-0/+1
| | | | state change alerts
* Support logging to a logfileTom Ritter2017-02-101-0/+1
|
* Only notify on failures and successes after the number of failures requiredTom Ritter2017-02-011-1/+3
|
* Add a new nomail commandline option for debuggingTom2016-09-141-0/+1
|
* Fixing a typo that was breaking a bunch of stuff.Tom Ritter2016-02-021-1/+1
|
* Add in the friendly name to the state file for debuggingTom Ritter2016-02-021-1/+1
|
* Fix the super() callingTom Ritter2016-01-311-1/+1
|
* Get custom state names for each of the jobs nowTom Ritter2016-01-311-1/+1
|
* Correcting a few small errorsTom Ritter2016-01-311-1/+1
|
* Refactor lots of things to allow you to be notified every so often, instead ↵Tom Ritter2016-01-311-5/+50
| | | | of every single time.
* Do not error if we can't hit localhostTom Ritter2016-01-251-2/+10
|
* Initial commit of checkerTom Ritter2016-01-251-0/+35