JobScheduler can make the start of a job chain dependent on the execution of previous jobs and job chains.
The following links describe the use of scripts to check job and job chain histories via the JobScheduler's XML interface before starting a job chain:
Display feature availability StartingFromRelease 1.10.2
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JITL-228
There are a number of methods available for configuring the parallel execution of job chains:
- For the configuration of job chains whose execution is dependent on the completion of preceding jobs job chains and orders:
- Using a
check_predecessor_job_chainjob :
(Method uses a job script to check the job chain and order histories for successful execution.)
- Using Scripting and Pre-/Post-Processing
(Method uses job monitors to check the job chain and order histories.)- i.e. using a job monitor script- How to manage complex conditions to check previous job executions and to start successor job chains
(Method checks job histories for successful execution.) - How to check previous job chain executions and to start successor job chains
(Method checks job chain and order histories for successful execution.) - How to add conditions for job execution with date calculation
(Method uses individually scripted conditions to determine job execution.)
- How to manage complex conditions to check previous job executions and to start successor job chains
- For a detailed description of the scripts and history objects used see:
- Using a
- For more information about configuring workflow dependencies see:See also:
- How to Execute Jobs in a Job Chain in Parallel
- Serial Job Execution with Locks (a similar page to the current page that is yet to be made)
- Use Cases - Dependency PatternsHow to Serialize the Execution of Jobs and Orders
| Display children header |
|---|
Further Resources
...
| Display content by label | ||||
|---|---|---|---|---|
|
...