job run get
Retrieve the information for a single job run from a specific project or space (either project_id or space_id must be set).
Syntax
cpd-cli job run get \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-config-location>] \
[--jmes-query=<jmespath-query>] \
--job-id=<job-id> \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
--profile=<cpd-configuration-profile-name> \
[--project-id=<cpd-project-id>] \
[--quiet] \
[--raw-output=true|false] \
--run-id=<job-run-id> \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The job run get
command has no
arguments.
Options
Option | Description |
---|---|
--context |
Specify the configuration context
name.
|
--cpd-config |
The Cloud Pak for Data
configuration location (for example, $HOME/.cpd-cli/config).
|
--cpd-scope |
The Cloud Pak for Data space, project, or catalog scope (for example, cpd://default-context/spaces/7bccdda4-9752-4f37-868e-891de6c48135).
|
|
Display command
help.
|
--jmes-query |
Provide a JMESPath query to customize the output.
|
--job-id |
Specify the job ID. Each job has a unique ID. Alternatively, the serving_name value can be used.
|
--output |
Specify an output format.
Valid formats include json, yaml, or text (the default
format).
|
--output-file |
Specify a file path where all output is redirected.
|
--profile |
The profile-name from the Cloud
Pak for Data configuration.
|
--project-id |
Specify a Cloud Pak for Data project instance.
|
--quiet |
Suppress verbose messages.
|
--raw-output |
When set to true, single values in
JSON output mode are not surrounded by quotes.
|
--run-id |
Specify a job run ID. The job run ID can be used to search the parent job of a job run.
|
--space-id |
Specify a space identifier.
|
--verbose |
Logs include more detailed
messages.
|
Examples
Note: The following examples use environment variables. Use a script to create
environment variables with the correct values for your environment. You can optionally add the
listed environment variables to the install variables script. For more information, see Best practice: Setting up install variables.
- Specify the environment variables in a script file.
-
job_id = <The unique job identifier> project_id = <The Cloud Pak for Data project instance> run_id = <The job run identifier>
- Retrieve a notebook run status.
-
cpd-cli job run get \ --jmes-query="entity.job_run.state" \ --job-id=${job_id} \ --output=json \ --project-id=${PROJECT_CPD_INSTANCE} \ --raw-output \ --run-id=${run_id}