AcademySoftwareFoundation / AcademySoftwareFoundation/rez

Suite management

Open
#435 0 comments 0 reactions 0 assignees View on GitHub
question rez-suite
Dominant language
Python
Stars
1.1k
Forks
369
Avg merge
12d 3h
Merged PRs (30d)
5

Description

In our department at Sony, we have a single suite containing a number of contexts that a single person has been managing.

However, we are at the point where we need a better solution and I was wondering how other facilities manage context and suite creation. My current thinking is to have the gatekeepers define a list of packages in a file (e.g. YAML), and automate the context and suite creation from them. The YAML files would be managed using source control, providing a history of changes, as well as a consistent way to reproduce suites if the need arises.

I'm curious how other facilities are handling their suites, and if there are any lessons to be learned from their experiences. The big question we are facing now is whether to have a single monolithic suite for everything, or to segment them per department/DCC. Its easier for us to have a single suite with lots of contexts, mainly because appending to `PATH` is painful, but it also keeps things simple as well.

Any comments would be much appreciated :)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.