Expose package orderers in rez config #868
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR add a
package_orderers
entry in the rez config. Fixes #329.This allow package orders to be configured.
We deployed this at RodeoFX 6 month ago and had no issues.
Our use case was to set a
per_facility
orderer so that rez "prefer" python 2 over python 3 by default.Here's what our configuration look like:
Changes
PackageOrderList
(similar toPackageFilterList
)VersionSplitPackageOrder
(second point in Orderer fixes #413)test_package_orders.py
for package orderers tests (100% branch coverage onpackage_orderers.py
. Note thattest_9
intest_packages.py
was moved into individual per-family tests.TimestampPackageOrder
rank default to 0 if unset