CI/CD Pipeline Bottleneck and Test Flakiness Analytics Plan

Role: Senior Release Analytics Engineer with 10 years experience optimizing build pipelines and developer productivity engineering.

Context

• Codebase structure: {{repo_scale_and_type}}
• Pipeline runtime: {{ci_platform_name}}
• Current performance baseline: {{median_build_duration}}
• Test unreliability: {{flaky_test_ratio}}
• Deployment velocity: {{weekly_deployment_frequency}}
• Runner infrastructure: {{tooling_budget_tier}}

Task

Produce a CI/CD performance analytics and stabilization plan to diagnose build pipeline bottlenecks, quantify {{flaky_test_ratio}} test instability, and reduce {{median_build_duration}} runtime.

Method

1. Map the CI workflow graph within {{ci_platform_name}} to identify serialization points and un-cached dependency pulls.
2. Define structured event logging for build job initiation, runner queue time, compilation, and test execution phases.
3. Establish telemetry collection for test-suite runtimes in {{repo_scale_and_type}} to isolate outlier tests.
4. Formulate a statistical flakiness index to isolate non-deterministic failures from legitimate code breaks.
5. Design pipeline parallelization and caching strategies optimized for the {{tooling_budget_tier}} runner model.
6. Outline automated dashboard reporting to give visibility to the team managing {{weekly_deployment_frequency}} releases.
7. Create a 4-week execution roadmap with clear metric milestones for build time and pass-rate predictability.

Constraints

• MUST prioritize solutions compatible with {{ci_platform_name}} native instrumentation or open standards.
• MUST NOT suggest upgrading runner tiers beyond {{tooling_budget_tier}} parameters without data justification.
• Plan MUST contain distinct measurement metrics for test flakiness versus compilation overhead.
• All recommendations must directly target the reduction of {{median_build_duration}}.

Output format

1. Baseline Analytics Diagnosis (1 summary paragraph)
2. Telemetry & Metric Definition Matrix (Markdown table: Metric Name, Data Source, Success Threshold)
3. 4-Week Pipeline Optimization Roadmap (Weekly breakdown: Objectives, Analytics Hooks, Expected Gains)
4. Flakiness Quarantine Protocol (3 concise actionable rules) Total length: 450-650 words.

Self-review

• Ensure the plan addresses both duration bottlenecks and the {{flaky_test_ratio}} rate.
• Confirm the runner constraints in {{tooling_budget_tier}} are respected.
• Verify all 6 variables are referenced accurately.