What CI queue time can tell you, and what it cannot , September 11 study

A September 11 study separating CI runner scarcity, scheduling delay, slow jobs, retries, and incomplete pull requests without scoring developers.

What CI queue time can tell you, and what it cannot , September 11 study
WORK_LANE / RESEARCH BRIEF / RELEASEREVIEW QUEUEACCEPTANCEPASSowner review requiredEVIDENCE TRAILTICKET → BRANCH → REVIEW → CLIENT RELEASE
Table of contents
  1. Research context
  2. Practical application
  3. Operating controls
  4. Sources
  5. Frequently asked questions

Research context

A build can wait because no runner is free, because a concurrency rule blocks it, or because an earlier workflow still owns the slot. Treating all of that time as test execution hides the part a team can change.

GitHub documents runner queues and concurrency controls. DORA studies delivery as a system. Those sources support separating queue states from execution states, but they do not supply a universal acceptable wait time.

Practical application

Method: select one repository and a fixed observation window. Record workflow creation, eligibility, runner assignment, job start, completion, cancellation, event type, and concurrency group. Split ordinary changes from urgent repairs before calculating a median and an upper percentile.

Scope and inference limits: the result describes the sampled workflows and runner pool. It may reveal capacity pressure or a blocking rule. It does not measure developer effort, test quality, or the value of a change.

Operating controls

Limitations: reruns, cancellations, changed runner labels, and missing timestamps can distort the sample. Publish the count and exclusions. The company owner retains runner purchasing and release policy.

Sources

  1. GitHub Actions hosted runners
  2. GitHub Actions concurrency
  3. DORA research

Frequently asked questions

What should happen first?

Begin with a bounded ticket, approved access, explicit acceptance evidence, and a named reviewer.

Who approves production changes?

The client's technical owner keeps final merge and release authority.

Build a programming lane your technical owner can review.

Bring the stack, backlog, acceptance checks, and release boundaries. We will help scope the role around the work.

Discuss your programming needs