Job Features: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
Created page with "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...." |
No edit summary |
||
| Line 1: | Line 1: | ||
In Espresso, everything starts with jobs. They can be scheduled, constrained by parameters even constrained to running on specific hosts. | 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 constrained by parameters. Parameters allow for many varying instances of the same job class that differ by the specified parameters. See [[Implementing_Jobs#Parameterization]]. | ||
=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 [http://en.wikipedia.org/wiki/Cron Cron]. | |||
Revision as of 03:56, 21 February 2011
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.
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.
