User Story

As a maintainer/developer of the OpenShift Jenkins images, i do not want to have to dig through old/unused code, files, Dockerfiles etc to make updates and enhancements.

• Anything related to rhel7 (specifically Dockerfiles)
• Agents that are no longer supported (maven, nodejs)
• Unused scripts

<link documentation of what is no longer supported - Corey>

Acceptance Criteria

• A team reviewed and merged pull request to openshift/jenkins repository
• CI passing
• CPaaS images pass Phase I and Phase II (when it is ready) verification
• Backported through to 4.11

Does NOT include

• Updating the main README.md for the repository

QE Impact

No impact to QE team

Docs Impact

Review of product documentation relating to Jenkins Images to ensure they do not reference any of the removed items

<insert links to official documentation>

PX Impact

No direct PX impact

Launch Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Notes

Add pertinent notes here:

• Enhancement proposal link
• Previous product docs
• Best practices
• Known issues

Guiding Questions

User Story

• Is this intended for an administrator, application developer, or other type of OpenShift user?
• What experience level is this intended for? New, experienced, etc.?
• Why is this story important? What problems does this solve? What benefit(s) will the customer experience?
• Is this part of a larger epic or initiative? If so, ensure that the story is linked to the appropriate epic and/or initiative.

Acceptance Criteria

• How should a customer use and/or configure the feature?
• Are there any prerequisites for using/enabling the feature?

QE Impact

• How can QE verify the story works as intended?
• Can QE automate some or all of the verification?

Docs Impact

• What documentation will users need to utilize the feature in the story?
• Who will write the docs? Who will edit/approve the docs, and when?

PX Impact

• Will customers need supplemental materials beyond documentation?
• Will CEE/support need any additional materials to debug this feature or help a customer?

Notes

• Is this a new feature, or an enhancement of an existing feature? If the latter, list the feature and docs reference.
• Are there any new terms, abbreviations, or commands introduced with this story? Ex: a new command line argument, a new custom resource.
• Are there any recommended best practices when using this feature?
• On feature completion, are there any known issues that customers should be aware of?