-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
2
-
False
-
-
False
-
-
-
1
-
Builds Sprint #24, Builds Sprint #25, Builds Sprint #26, Builds Sprint #30
-
4
Story (Required)
As a developer trying to release new version (major, minor, patch) I want to automate the FBC generation.
Background (Required)
Right now, we are manually generating catalog and adding the FBC graph. This process is time consuming and error prone. We need to automate the process the generate FBC through a script.
Out of scope
TBD
Approach (Required)
- Create a script the update the existing FBC graph with the latest and the required bundles.
- The script should handle upgrade path, deprecation and removal bundle and channel
- Generate the test catalog to test
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