OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• Provide cluster-level dashboards for Build (v1) usage
• Obtain accurate success/failure metrics for builds (v1)

Why is this important?

• Initial telemetry data suggests that builds are used very differently across clusters. Some clusters have thousands of build objects, others a few dozen.
• We have no accurate reporting on how many builds are actually being run, and how many succeed/fail. This is due to pruning that happens by default on clusters.

Scenarios

As an engineer
I want to drill down on build usage by cluster
So that I can have a detailed view on which kinds of builds a customer is using

As a product manager
I want to know if customers are having a positive or negative experience with builds
So that I can understand the user's product experience

Acceptance Criteria

• Telemetry dashboards have a cluster detail view for builds
• Telemetry can accurately report successful or failed builds

Dependencies (internal and external)

1. Monitoring

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>