Jobber is a utility for Unix-like systems that can run arbitrary commands, or “jobs”, according to a schedule. It is meant to be a replacement for the classic Unix utility cron.
Along with the functionality of cron, Jobber also provides:
- Job execution history: you can see what jobs have recently run, and whether they succeeded or failed.
- Sophisticated error handling: you can control whether and when a job is run again after it fails. For example, after an initial failure of a job, Jobber can schedule future runs using an exponential backoff algorithm.
- Sophisticated error reporting: you can control whether Jobber notifies you about each failed run, or only about jobs that have been disabled due to repeated failures.
Jobber is stable. Production releases have been made.
Bug reports and feature requests are welcome; please report them on Jobber’s GitHub site.
Please post more open questions or comments on the mailing list.
Contributions are welcome as well!
Like cron, Jobber enables different users to run their own sets of jobs. The main security requirement is that Jobber does not enable users to do something they otherwise would not be allowed to do. In particular, the set of commands that a user can execute via Jobber must be a subset of the set of commands that the user can execute in the shell.
Note that Jobber has not been thoroughly and expertly reviewed with regard to security. (Of course, neither has most software....) Meeting its security requirements is indeed a goal, but, as made clear in the license, the authors make no guarantee that there are no vulnerabilities in Jobber.