Use job environments on Deadline Cloud
The following job bundles supplement the
Control the job environment with OpenJD queue environments section in the developer guide.
Each bundle demonstrates a different way to use
Open
Job Description environments
- job_env_vars
-
Sets environment variables through a job environment.
- job_env_with_new_command
-
Wraps the task command through a job environment.
- job_env_daemon_process
-
Runs a background daemon process alongside the task.
- pip_self_contained_job
-
Defines a job environment that creates a Python virtual environment with
pipand adds it to thePATHfor the job's steps, with no queue environment required. Runs on any Linux worker withpython3available, including Deadline Cloud service-managed fleet workers. - pip_package_job
-
Provides the job's Python dependencies through the Pip queue environment for Deadline Cloud instead of a job environment. The job only sets the
PipPackagesparameter that the queue environment reads. Use this style to define the pip environment once and share it across many jobs on a queue.
For more queue-level environment examples, see Queue environment examples for Deadline Cloud.
