-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
2
-
False
-
-
False
-
-
-
Builds Sprint #24, Builds Sprint #25, Builds Sprint #26, Builds Sprint #30, Builds Sprint #31, Builds Sprint #32
-
6
Story (Required)
As a developer trying to release a new minor or z-stream release of OpenShift Builds I want to automate the updated required for the CSV.
Background (Required)
Right now we are manually updating the CSV before releasing an update. This process is error prone and time consuming, hence requires some automation to make it simpler to do release and test bundle.
Out of scope
TBD
Approach (Required)
- Create a script to update CSV parameters (Related images digest, version)
- Generate bundle to test (should have image references from staging)
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met
- links to
1.
|
Update "relatedImages" section |
|
Closed | |
Sayan Biswas |