-
Epic
-
Resolution: Done
-
Major
-
None
-
4.16
-
Jenkins Supportability Enhancements
-
False
-
None
-
False
-
Green
-
Done
-
SECFLOWOTL-23 - Simplify Jenkins release process
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- The goal of this Epic is to provide a minimum acceptable set of enhancements to our Jenkins repositories and CI/CD pipelines that will increase their supportability.
Why is this important?
- This is important because it will save us time and resources in future Sprints, along with being easier to round robin support tasks within the team.
Scenarios
- Updating plugins and core Jenkins version to mitigate CVEs.
- Building, testing and releasing new images via CPaaS.
- Supporting future OpenShift releases.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- A new associate can walk through the documentation and perform the following tasks:
-
- Update plugins and core Jenkins version to mitigate CVEs.
- Build, Test and Release new Jenkins images.
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
1.
|
Enhancement proposal created and approved | Closed | Unassigned | ||
2.
|
Stories created and fleshed out | Closed | Unassigned | ||
3.
|
Epic and stories presented to team and discussed | Closed | Unassigned |