Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix executions that stomped on each other | Tom Ritter | 2017-11-11 | 1 | -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. | ||||
* | Clarify the job inheritance info and make the state file simpler | Tom Ritter | 2017-02-01 | 1 | -1/+1 |
| | |||||
* | Create an option that lets you require two failures before alerting. | Tom | 2016-12-28 | 1 | -0/+2 |
| | |||||
* | Update readme | Tom | 2016-09-14 | 1 | -3/+0 |
| | |||||
* | Update the crontab entries | Tom Ritter | 2016-07-12 | 1 | -1/+1 |
| | | | The 'Run daily at noon' was actually "Run at midnight on the twelve day of the month" | ||||
* | Get custom state names for each of the jobs now | Tom Ritter | 2016-01-31 | 1 | -1/+3 |
| | |||||
* | Refactor lots of things to allow you to be notified every so often, instead ↵ | Tom Ritter | 2016-01-31 | 1 | -11/+12 |
| | | | | of every single time. | ||||
* | Update README with some clarifications. | Tom Ritter | 2016-01-27 | 1 | -2/+1 |
| | |||||
* | Update README.md | Tom Ritter | 2016-01-27 | 1 | -2/+70 |
| | |||||
* | Make Readme markdown | Tom Ritter | 2016-01-27 | 1 | -0/+10 |