rez-resolvev1.0.0

A pipeline TD at a VFX studio is investigating why nightly rez-env resolves intermittently fail across shows. They enable -v to read solver scopes, EXTRACT/INTERSECT/REDUCE steps, and conflict markers, then use rez-depends to find the package introducing a conflicting python or Maya requirement. The goal is to fix upstream package requirements so artists' environments resolve reliably.

A build engineer at a game studio needs to explain a previously solved resolve by inspecting context.rxt, dependency graphs, and source order. They use rez-context --dependency-graph and --print-graph to trace which package version was selected and why, then document the result for build reproducibility. This prevents 'works on my machine' drift between art and engineering teams.

A technical artist encounters unexpected variant selection when a package supports multiple DCC integrations. They enable -v to see scope syntax like [foo-1.2.0[0,1]] and REDUCING output, then pin the discriminator or adjust variant_select_mode. This ensures the correct variant (e.g., Maya vs Houdini) is picked without changing the package itself.

An infrastructure engineer migrating a studio from CentOS to Rocky Linux hits cyclic dependency errors during re-resolve. They follow the triage workflow: reproduce with rez-env --output, inspect the failure graph, bisect the request, and only then escalate to -vvv. The output from SPLIT and phase stack comments helps them identify which packages created the loop.

A pipeline developer adding a new third-party library to a studio's rez ecosystem needs to validate it against existing constraints. They use -v to understand extraction/merge behavior, rez-search to check versions, and --max-fails N to collect multiple conflicts at once. This speeds up onboarding packages without breaking existing show environments.

Studios hire external pipeline TDs to diagnose and fix rez resolve issues, optimize package repos, and train internal teams on solver internals. The work is scoped as audits, remediation projects, or retainer support for production deadlines.

Course creators and studios offer workshops on rez solver internals, reading -v output, and building robust package ecosystems. Content is sold as self-paced video courses, live cohort training, or team bootcamps.

A hosted service provides curated, pre-resolved rez package repositories with dependency graphs and conflict resolution guarantees. Studios subscribe to reduce local infrastructure overhead and ensure consistent resolves across distributed teams.