-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
builder image advertises constraints
-
False
-
-
False
-
Not Selected
-
To Do
-
RHELAI-1893 - support building wheels for multiple products
-
100% To Do, 0% In Progress, 0% Done
Goal:
Provide high-level goal statement; providing user context and expected user outcome(s) for this Epic. 2-3 sentences...
- Include information in the builder image about constraints that should be applied for key components (like torch), especially when the image is only able to build a single version of a package.
- Use that constraint information in the wheel build pipeline instead of requiring consumers of the image to manage those constraint updates separately.
Acceptance Criteria:
The Acceptance Criteria provides a definition of scope and the expected outcomes - from a users point of view - defines the value proposition
- A consumer of a builder image can change versions of the image and start building a new version of a constrained package without having to manually edit the constraints file for the collections built in the pipeline.
- The built-in constraints should be incorporated automatically into all builds.
- Consumers of the builder image can provide additional constraints, for packages not included in the default constraints.
- It is an error for the consumer of the builder image to change a constraint built into the builder image. This rule is enforced with a test job in the pipeline repo before changes to the constraints file are merged.
Open questions:
Any additional details, questions or decisions that need to be made/addressed
- <your text here>
- ...
- depends on
-
RHELAI-2352 builder test cache index
- In Progress