| Table of Contents |
|---|
Use of 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.
Job Patterns
Independent Job Start Pattern
- Jobs are completely independent from one another.
- Each job has an individual start time.
| Flowchart |
|---|
Job1 [label="Job 1",fillcolor="lightskyblue"]
Job2 [label="Job 2",fillcolor="lightskyblue"]
Job3 [label="Job 3",fillcolor="lightskyblue"] |
Job Start Pattern based on Execution Results
- Jobs are started based on the execution result of a previous job.
- If Job 1 returns an exit code 1 then Job 2 will be executed.
- If Job 1 returns an exit code 2 then Job 3 will be executed.
| Flowchart |
|---|
Job1 [label="Job 1",fillcolor="lightskyblue"]
Job1_Exit_Code [shape="diamond",label="Exit Code",fillcolor="white"]
Job2 [label="Job 2",fillcolor="lightskyblue"]
Job3 [label="Job 3",fillcolor="lightskyblue"]
EndStateSuccess [label="End state: success",fillcolor="palegreen"]
EndStateError [label="End state: error",fillcolor="lightcoral"]
Job1 -> Job1_Exit_Code
Job1_Exit_Code -> EndStateSuccess
Job1_Exit_Code -> Job2 [label=" in case of exit code 1 \n start job 2 "]
Job1_Exit_Code -> Job3 [label=" in case of exit code 2 \n start job 2 "]
Job1_Exit_Code -> EndStateError |