Epic Goal

Maintain our distribution of Jenkins for OpenShift as a platform aligned container image through CY 2025.
This is a time-bound, "keep the lights on" epic to track features that must be delivered in the OCP 4.18, 4.19 release cycles.

Timeline

CY 2025

Dependencies

None

Customer Need

Internal: keep CPaaS online as teams transition to Konflux

External:

• Customers who use Jenkins for their CI/CD and DevOps workflows.
• Platform for Jenkins integrations in other Red Hat products (ex: potential plugin for RHTAP on-prem)

Success Criteria

What is the success criteria for this strategic outcome?  Avoid listing Features or Initiatives and instead describe "what must be true" for the outcome to be considered delivered.

• Jenkins remains functional on OpenShift
• Customers can upgrade to supported LTS versions of Jenkins in their deployments

Expected Results (what, how, when)

• Scale the core: continue renewals for OCP customers that rely on Jenkins for their CI/CD
• TODO: how can we identify which renewals rely on continued Jenkins support?
• Continue test/certification of Jenkins support on OCP
• Security patching for Jenkins CVEs - core and plugins

Metrics

Possible Measurements / Observable Results: Detailed overview of what will be measured to identify progress on that outcome.

• Versions of OpenShift that Jenkins supports. Goals: OCP 4.18, 4.19
• Time to delivery: how long between OpenShift version GA and Jenkins image availability? Goal: 5 business days or less.
• Mean time to remediation (MTTR) for CVEs by severity and supported OCP version. Goal: meet official "SLAs" from Product Security

Post Completion Review – Actual Results

After completing the work (as determined by the "when" in Expected Results above), list the actual results observed / measured during Post Completion review(s).