Skip to content
An alternative to cron, with sophisticated status-reporting and error-handling
Branch: master
Clone or download
dshearer Merge pull request #241 from gadget/client-timeout-option
adding timeout option to cmds, instead of fixed 5s
Latest commit 8f9fb6a Apr 13, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Bump required Golang ver to 1.11 Apr 13, 2019
buildtools Improve Makefiles Jan 13, 2018
common (#202) Support macOS Nov 12, 2018
ipc adding execution time to runlog Mar 27, 2019
jobber Merge branch 'master' into client-timeout-option Apr 13, 2019
jobbermaster
jobberrunner adding execution time to runlog Mar 27, 2019
jobfile fixing tests Mar 27, 2019
mk make-release-notes.py: Add Feb 2, 2019
packaging Merge pull request #250 from dshearer/master Apr 13, 2019
platform_tests Merge branch 'master' into issue-189 Nov 24, 2018
smoke_tests (#183) Support receiving cmds from net socket Mar 17, 2018
vendor Replace Godep with dep Feb 21, 2018
.gitignore Merge branch 'master' into issue-189 Nov 24, 2018
.travis.yml Use vagrant; use docker only for smoke test Sep 17, 2017
Gopkg.lock Replace Godep with dep Feb 21, 2018
Gopkg.toml Replace Godep with dep Feb 21, 2018
LICENSE LICENSE: Added "Charles" to my name. Sep 13, 2014
Makefile Bump required Golang ver to 1.11 Apr 13, 2019
README.md README.md: Remove reference to Ubuntu readme Jan 14, 2018
make-release-notes.py make-release-notes.py: Add Feb 2, 2019
version Bump version to 1.4.0 Apr 6, 2019

README.md

Jobber Build Status CII Best Practices

A replacement for cron, with sophisticated status-reporting and error-handling.

Intro

Jobber is a lightweight 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.

Contributing

Contributions/suggestions/requests are welcome! Feel free to open an issue, or ask a question on the mailing list.

More Info

More info can be found on Jobber's website.

You can’t perform that action at this time.