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

1. Updating plugins and core Jenkins version to mitigate CVEs.
2. Building, testing and releasing new images via CPaaS.
3. 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::

1. …

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>