Today I was going to switch gears into Pyblish, and keep an eye on the testing that's going on with Rez and Allzpark. Testing revealed a number of undocumented features and fair amount of bugs.
Here are the things that were missing from the documentation, along with parts I haven't yet filled in.
- How to test a package
- Reproduce an environment on a render farm
- Multiple versions of an an application
- Multiple packages in the same Git repository
- Managing packages with git
- How to test the contents of a package
One of the early issues of tailoring packages was figuring out how to interpret errors.
Exhibit A
The context failed to resolve:
The following package conflicts occurred: (python-3.7 <--!--> python==2.7.16)
Can you tell which package to investigate? I've logged an issue about this here.
Exhibit B
RexUndefinedVariableError: Referenced undefined environment variable: PROJECTS_PATH
Can you tell which package referenced this variable? It is another instance of too little information coming out of a resolve, logged an issue here.
Raf encountered an untested area of Rez related to Python 3.
catching classes that do not inherit from BaseException is not allowed
Fixed and deployed this, logged here.
We also found that the project version specified didn't always get resolved, I found this was due to an oversimplistic interpretation of the project/application combination of Allzpark. Fixed and logged here.
There are few things left to document, and a new feature requirement; being able to launch two or more versions of the same application, such as Maya 2018 and 2019.