Managing Job Runs
Learn about job run details, canceling, and cloning them.
Job Run Details
Managing job runs is similar to managing jobs. You can view, edit, move, clone, cancel, delete, and add tags to Data Science job runs. The operations are the same though when you edit job runs, you can only change the name.
When you view a job run, the information tab appears the job run information including:
-
Who created the job run.
-
When the job run was accepted, started and finished.
-
Job run OCID.
-
Logging details if it was enabled.
-
Infrastructure configuration including the VM shape name, the subnet OCID, and the storage size.
If storage mounts exist, then those details are displayed. The storage mounts can't be changed in a job run though can be edited in the job.
The runtime configuration tab displays any command line arguments, maximum runtime minutes, and environment variables that were specified. Both the default and override configurations are displayed.
From the Tags tab, you can view the tags that have been applied to the job. To update or remove a tag, find the tag you want and click the pencil button next to it. Enter the new tag then save it or remove the tag by clicking Remove Tag.
You use the Jobs resource to manage job runs.
Canceling Job Runs
Only job runs that are in ACCEPTED, IN_PROGRESS, or
NEEDS_ATTENTION states can be canceled.
You can either click the job run's name or the Actions menu, and click Cancel to cancel the job run.
Cloning Job Runs
In the Console, you can clone a job run to use the same run as a basis for a new run that you want to change configurations to get different results. Cloning lets you to start several jobs runs to run in succession with varied results.
Cloning is only available in the Console.
Using the API
Use the following operations to manage job runs:
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.