There were 2 issues that I noticed on the 2 scripts:
create_adaptor_packaging_artifact.sh was incorrectly using the RUNTIME_INSTALLABLE as openjd-adaptor-runtime-for-python instead of openjd-adaptor-runtime.
depsBundle.sh had a typo in the package name and used deadline_cloud_for_cinema4d_submitter instead of deadline_cloud_for_cinema_4d_submitter.
What was the solution? (How)
Fixed the typos and confirmed that the scripts were working successfully.
And running the scripts created the dependency bundles in the dependency_bundle folder.
What is the impact of this change?
This will help with our release process.
How was this change tested?
Here's the output from running the create_adaptor_packaging_artifact.sh script.
What was the problem/requirement? (What/Why)
There were 2 issues that I noticed on the 2 scripts:
create_adaptor_packaging_artifact.sh
was incorrectly using theRUNTIME_INSTALLABLE
asopenjd-adaptor-runtime-for-python
instead ofopenjd-adaptor-runtime
.depsBundle.sh
had a typo in the package name and useddeadline_cloud_for_cinema4d_submitter
instead ofdeadline_cloud_for_cinema_4d_submitter
.What was the solution? (How)
Fixed the typos and confirmed that the scripts were working successfully.
And running the scripts created the dependency bundles in the
dependency_bundle
folder.What is the impact of this change?
This will help with our release process.
How was this change tested?
Here's the output from running the
create_adaptor_packaging_artifact.sh
script.This also created
cinema4d-openjd-py3.11-linux-64-0.3.4.dist-info.tar.gz
file.Here's the output from running the
depsBundle.sh
script.Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.