Epic Goal

Ensure Jenkins can be built and deployed onto OCP 4.16 with a "4.16.z" tag.

Note: Starting with OCP 4.15, we are providing support for Jenkins on an "N+1" version of OCP. Ex: Jenkins 4.15 tagged images are supported on OCP 4.16.

Advisories for Jenkins in the OCP 4.16 release cycle will be tracked in JKNS-459, unless the release is tied to a separate epic/initiative.

Why is this important?

We must ensure supported products work on the latest GA-ed version of OCP

Scenarios

1. Customer runs Jenkins on OCP 4.16 for CI/CD
2. Red Hat internal systems that operate Jenkins on OCP 4.16

Acceptance Criteria (Mandatory)

• Jenkins builds pass internal checks to run on OCP 4.16
• CI verifies Jenkins can run on OCP 4.16

Dependencies (internal and external)

TBD - are there dependent plugin/library updates (ex: fabric-8 Kuberenetes client?)

Previous Work (Optional):

Open questions:

• Any hard base image requirements for OCP 4.16?
• Any breaking changes in our dependencies?

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment