CONCEPT Cited by 1 source

Build reliability

Build reliability is the developer-facing metric for how often a build (CI pipeline on the main / target branch) succeeds. Closely related to concepts/ci-reliability but framed from the developer's experience side: "when I pull from main and try to build, does it actually build?".

Low build reliability compounds into:

• Local dev-environment breakage (my pull from main includes someone else's broken merge).
• Blocked rebases on other in-flight PRs.
• On-call firefighting cycles — the unreliability is felt as incidents, not just CI-dashboard failures.
• Developer-satisfaction cost — typically tracked via explicit survey.

Atlassian tracks developer-satisfaction on build reliability as a top-line metric. Jira repo disclosed: 70% → 82% satisfaction lift after Bitbucket Merge Queues rolled out, and 3–5 incidents/week → rare edge cases only. (Source: sources/2026-04-29-atlassian-inside-atlassians-merge-queues)

Seen in

• sources/2026-04-29-atlassian-inside-atlassians-merge-queues — 70% → 82% build-reliability satisfaction on the Jira repo after merge-queue adoption.

Related

• concepts/ci-reliability
• concepts/semantic-merge-conflict
• concepts/merge-queue
• concepts/developer-velocity
• concepts/trunk-based-development
• patterns/validate-against-future-state-of-main
• patterns/eject-failing-pr-keep-queue-running
• systems/bitbucket-merge-queues
• systems/bitbucket-pipelines
• companies/atlassian