Build Pipeline Metrics

CI/CD pipeline performance — build time breakdown, weekly success rate, failure counts by repo

Build Pipeline Metrics — CI/CD Performance

Ten weeks of pipeline data across five repos. No theories. Just results.

5 Repos tracked
94% Avg success rate
120s Longest build
32 Failures (10 wk)

Build time breakdown

Seconds per phase across all tracked repos — compile, test, deploy. Max is 120s (agentic-semantic-web). Test dominates every build. That's expected. Don't cut your test suite to make this chart look better.

Build time breakdown — seconds per phase (max 120s)
CompileTestDeploy
agentic-semantic-web 21s 80s 19s
api-gateway 12s 65s 22s
trentuna-web 18s 55s 15s
commons 15s 45s 12s
vault 8s 30s 10s

Segment totals: asw 120s · api-gateway 99s · trentuna-web 88s · commons 72s · vault 48s

Weekly build success rate

Percentage of successful builds per week over the last ten weeks. Week 8 hit 100%. That's the target. Everything else is noise telling you where to look.

Build success rate — weeks 1–10 (max 100%)
W194%
W288%
W391%
W478%
W595%
W682%
W796%
W8100%
W989%
W1097%

W4 dip: flaky integration test on api-gateway, fixed W5. W6 dip: deploy timeout regression, fixed W7.

Failure count by repo

Total build failures over the last ten weeks. Two repos are over the acceptable threshold. They're marked. Fix them.

api-gateway and agentic-semantic-web are above threshold. Both repos averaged more than one failure per week. api-gateway has the most — 14 failures in 10 weeks. That's not a fluke. That's a structural problem.
Build failures — last 10 weeks (max 14, api-gateway)
api-gateway 14
agentic-semantic-web 9
trentuna-web 5
commons 3
vault 1

Threshold: >7 failures in 10 weeks. vault and commons are solid. trentuna-web is borderline — watch it.