Story (Required)

As an Engineer within the Developer Tools Organization trying to deploy Jenkins images in a timely manner, I want to automate the gathering of Bugs, CVEs and Enhancements to include in the ERRATA that is published when we publish a new image.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

It is a time consuming and convoluted process to gather all of the Bugs, CVEs and Enhancements that are part of a new Jenkins release to enter into the ERRATA tool. We have so far automated (or at least mostly automated) many of the processes associated with releasing new Jenkins images and this is one of the last road blocks that we face on our path to releasing new images on a timely cadence.

Out of scope

Nothing has been identified.

Approach (Required)

Currently, we should investigate the Janitor Tool (github link below to enable it for testing).

Dependencies

No dependencies have been identified.

Acceptance Criteria (Mandatory)

1. Creation of the ERRATA for new Jenkins and Jenkins Agent Base images is automated using the Janitor Tool (or similar)
2. The process for creating ERRATA using the Janitor Tool (or similar) is documented in the Jenkins folder of our shared Team Google Drive

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met