Job Configuration File

Job-specific configuration parameters are stored in the job_config.yaml file in your workspace directory. The Robbie Python SDK reads the job_conf.yaml file to determine the funding_group_id, environment_id, and image in the following cases:

• `robbie run` (without –i option)

• `robbie run [commands]` - if the job_config.yaml file contains commands, the [commands] will be used instead.

• Notebook Runner

• Remote Function runs

You can use the `robbie configure` command or the `robbie run` command with the –i option to generate and write a job_config.yaml file.

Here’s an example job_config.yaml file.

The parameters are defined as follows:

• funding_group_id - String that contains the UUID of the funding group that the job will be billed against. For example, “cecfc347-5680-4fb0-ae99-b000941b08dd”

• environment_id - String that contains the UUID of the environment that the job will use. For example, “d26d6431-f1a5-4cea-b929-a4ed1f70eaaa”

• image - String that contains the image name or “auto-select”. By specifying “auto-select” Robbie will choose the correct image for you.

• commands – These are the Linux shell commands to be run.

• env – Environment variables and values (in key: value format) to be transferred to the remote machine and made available in the remote environment. If a value is not specified (key: ), the local environment variable will be read and sent to the remote machine.

Before you run starts, you can view these parameters in the Run configuration banner: