-
Epic
-
Resolution: Unresolved
-
Minor
-
None
-
builds-1.0
-
None
-
Build Strategy Catalog Experience
-
False
-
None
-
False
-
Not Selected
-
To Do
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- Define the type(s) of build strategy source catalog (tarballs, git repo, ociartifcats, artifcathub repository)
- Create and publish catalog repository to artifactHub
- Install shipwright strategies via the operator
Why is this important?
- Actually we provide build strategies as samples in the build repo. To improve user experience around shipwright, we should provide and an easy way to search and discover all strategy resources, we need then a repository of high-quality, community-contributed strategy resources. This is what we call the catalog.
- With Shipwright operator, the user installs the Shipwright Build Controller.
Installation and upgrade of Build Strategies and Cluster Strategies is currently a manual process. In order to improve user experience around Shipwright,the Shipwright Operator should also install the build strategies.
Scenarios
- ...
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment