fix: Add OCIO configuration to Job Environments

[diane-hj]

What was the problem/requirement? (What/Why)

• There are 3 ways to set OCIO configuration in Nuke: environment variable, custom config, and default config that is defined in Nuke already. The original implementation only took care of custom config. We want to handle when customer set their OCIO configuration in environment variable or default config.

What was the solution? (How)

• When OCIO is enabled, check the configuration path for all three options, then set the path via JobEnvironment in JobTemplate.

What is the impact of this change?

• When environment variable is set, the path will be set with environment variable
• When custom config is set, the path will be set with custom config
• When default config is set, the path will be set with default config

How was this change tested?

• Submitted the job with OCIO setup, and verified it rendered successfully
• Submitted the above job with different OCIO setup, verified it rendered successfully, and verified the output looks different in color scheme
• Submitted the job with OCIO environment variable, and verified it rendered successfully

Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.

Timestamp: 2024-09-16T22:51:08.146094-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/group-read

group-read
Test succeeded

Timestamp: 2024-09-16T22:51:08.578900-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/noise-saver

noise-saver
Test succeeded

Timestamp: 2024-09-16T22:51:08.968215-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/multi-load-save

multi-load-save
Test succeeded

Timestamp: 2024-09-16T22:51:09.358968-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/frame

frame
Test succeeded

Timestamp: 2024-09-16T22:51:09.757446-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/ocio

ocio
Test succeeded

Timestamp: 2024-09-16T22:51:10.157282-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/cwd-path

cwd-path
Test succeeded

All tests passed, ran 6 total.
Timestamp: 2024-09-16T22:51:13.578587-07:00

Was this change documented?

No

Is this a breaking change?

No - In Nuke, environment variable takes precedence over other ocio configurations. (Ex. When OCIO environment variable is set, updating custom config in UI is disabled with the message: OCIO environment variable is set. Setting OCIO configs from within Nuke will be disabled.)

The existing user who uses custom config will continue to work.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[sonarcloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud