Page History

...

Jobs

• Jobs are the basic unit for the processing of executable files, shell scripts, procedures 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 these features 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 this feature in the order and job chain documentation.

Orders

• Orders are triggers that will cause a job chain to start, e.g. by calendar events and by programmatically created events.
• Orders can be used with parameters that allow the same job chain to be used with different parameter sets.
• Workflows are ruled by orders. An order can be thought of as a directive that is processed in a chain of jobs. An order is assigned to a job chain with an identifier which is valid for that particular job chain. The order also has a status that changes after the processing of each job node and can have a payload of parameters.
• Orders are persistently stored during processing. If a job, job chain or order is stopped during processing and then restarted, it will be continued at exactly the point where it was stopped.

Job Chains

Orders

Operation

Resources

...