Job Features
In Espresso, everything starts with jobs. They can be scheduled, constrained by parameters, even constrained to running on specific hosts.
Jobs can be constrained by parameters. Parameters allow for many varying instances of the same job class that differ by the specified parameters. See Implementing_Jobs#Parameterization.
Jobs can be restricted to run only on specified hosts allowing you to use Espresso in a multi-host environment with jobs that can't be run on just any host.
Date bound schedule/states
Espresso supports setting the job's runtime schedule and state by date/time windows. Changes in either or both can be scheduled for the future and set indefinitely or reverting back to previous state at the completion of the window. This great functionality allows you to ensure that changes take place in advance without needing to babysit your running Espresso instances.
Scheduling is done using cron patterns Cron.
Recovery
Recovery Type allows you to specify how to handle a job that is not run within the pickup buffer because of a conflict or because the scheduler was not running.
- Last indicates that only the last missed job run will be recovered.
- Conflicted indicates that only conflicted job runs will be recovered.
- All indicates that all job runs will be recovered.
- None indicates that no job runs will be recovered.
Pickup Buffer allows you to indicate how many minutes after the scheduled time a job is considered valid for regular pickup.
