Chaining: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Espresso supports dynamic job chaining between two jobs. All chaining configuration is managed in the [[Job Chains]]. | Espresso supports dynamic job chaining between two jobs. All chaining configuration is managed in the [[Job Chains]] portion of the admin web application. | ||
A job can be chained to any other job. By default, chaining between two jobs will trigger when the source job either completes or fails, but any source termination state can be selected to trigger the chain. Chain configurations can be disabled and re-enabled at anytime. Chaining can also be constrained to a schedule, using a standard cron schedule. | A job can be chained to any other job. By default, chaining between two jobs will trigger when the source job either completes or fails, but any source termination state can be selected to trigger the chain. Chain configurations can be disabled and re-enabled at anytime. Chaining can also be constrained to a schedule, using a standard cron schedule. | ||
Revision as of 02:14, 21 February 2011
Espresso supports dynamic job chaining between two jobs. All chaining configuration is managed in the Job Chains portion of the admin web application.
A job can be chained to any other job. By default, chaining between two jobs will trigger when the source job either completes or fails, but any source termination state can be selected to trigger the chain. Chain configurations can be disabled and re-enabled at anytime. Chaining can also be constrained to a schedule, using a standard cron schedule.
