...
Excerpt |
---|
The JobScheduler's unique job and order concept includes the use organization of jobs within into job chains with and the use of dependencies. - Jobs are the basic unit for the processing of executable files (programs, scripts, commands etc.).
- Job chains Chains can be seen as an assembly line on which a number of job nodes are passed sequentially.
- Orders represent triggers that will cause a job chain to be started based on according to calendar events.
|
Jobs
- Jobs are the basic unit for the processing of executable files, shell scripts, commands and of job implementations based on the JobScheduler internal API.
- Jobs can be executed independently from one another. However, job starts can also be made dependent on the execution result (success, failure, exit code) of preceeding jobs.
- Jobs can be executed in parallel by a configurable number of tasks.
Read more on the features of Job Objects in the job documentation.
Job Chains
- Job chains can be seen as an assembly line on which multiple job nodes are passed, with each job making up one step in the processing of a chain.
- Job chains allow to reuse the same jobs in multiple job chains with different parameter sets.
- Job chains allow to map dependencies, e.g. by continued processing with different job nodes depending on the execution result of previous job nodes.
- Job chains enable complex workflow patterns such as Split & Sync, see Example showing the synchronization of multiple job chains
- Nested job chains can be used to control and parallelize the execution of multiple job chains.
Read more on the features of Job Chain Objects in the order and job chain documentation.
Job Chains
Excerpt Include |
---|
| Job Chains |
---|
| Job Chains |
---|
nopanel | true |
---|
|
Orders
Operation
Excerpt Include |
---|
| How do Job Chains work? |
---|
| How do Job Chains work? |
---|
nopanel | true |
---|
|
Resources
Display content by label |
---|
Type | Feature |
---|
Labels | jobscheduler feature job-and-order |
---|
|
...