Class JobExecution
Represents an execution of a job. The job execution can be accessed from a JobStepExecution via JobStepExecution.getJobExecution(). If a pipeline is used to implement a step the step execution is available in the pipeline dictionary under the key 'JobStepExecution'. If a script module is used to implement a step the step execution is available as the second parameter of the module's function that is used to execute the step, e.g.:
| Property | Description |
|---|---|
ID: String (read-only) | Returns the ID of this job execution. |
context: Map (read-only) | Returns the job context which can be used to share data between steps. |
jobID: String (read-only) | Returns the ID of the job this job execution belongs to. |
This class does not have a constructor, so you cannot create it directly.
| Method | Description |
|---|---|
| getContext() | Returns the job context which can be used to share data between steps. |
| getID() | Returns the ID of this job execution. |
| getJobID() | Returns the ID of the job this job execution belongs to. |
assign, create, create, defineProperties, defineProperty, entries, freeze, fromEntries, getOwnPropertyDescriptor, getOwnPropertyNames, getOwnPropertySymbols, getPrototypeOf, hasOwnProperty, is, isExtensible, isFrozen, isPrototypeOf, isSealed, keys, preventExtensions, propertyIsEnumerable, seal, setPrototypeOf, toLocaleString, toString, valueOf, values
- ID: String
(read-only) Returns the ID of this job execution.
- context: Map
(read-only) Returns the job context which can be used to share data between steps. NOTE: Steps should be self-contained, the job context should only be used when necessary and with caution. If two steps which are running in parallel in the same job store data in the job context using the same key the result is undefined. Don't add any complex data to the job context since only simple data types are supported (for example, String and Integer).
- jobID: String
(read-only) Returns the ID of the job this job execution belongs to.
- getContext(): Map
Returns the job context which can be used to share data between steps. NOTE: Steps should be self-contained, the job context should only be used when necessary and with caution. If two steps which are running in parallel in the same job store data in the job context using the same key the result is undefined. Don't add any complex data to the job context since only simple data types are supported (for example, String and Integer).
Returns:
- the map that represents the job context.
- getID(): String
Returns the ID of this job execution.
Returns:
- the ID of this job execution.
- getJobID(): String
Returns the ID of the job this job execution belongs to.
Returns:
- the ID of the job this job execution belongs to.