Epic Goal

• Continuously deliver code to market with high quality, high security, stability, and a high level of velocity.

Why is this important?

• A core deliverable of the ACM DevOps team is the modification, automation, operation, and delivery of downstream builds across the ACM family of Downstream Deliverables.

• This list is dynamic but currently includes ACM, MCE, Gatekeeper, IDP Config, Submariner, and VolSync.

Scenarios

1. maintain the downstream pipelines for these products across their active z-streams

1. decommission deprecated pipelines

1. develop and maintain automation to drive these build pipelines

1. enhance or extend the functionality of these downstream builds

1. kick-off new versions of these products with their accompanying downstream artifacts

1. create build pipelines and downstream artifacts for net new components/deliverables

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• <TBD>

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

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>