Measure queue and execution delay separately
The team calls CI slow from total duration, but most delay occurs before an executor starts during the morning burst.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Observability · Latency analysis
Estimated field mix
- DevOps70%
- Performance engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional TypeScript monorepo has twelve packages and a local CI simulator. Pull requests wait for redundant work, stale caches occasionally pass broken changes, and superseded runs continue consuming executors. Create synthetic package graphs and fake check APIs; no hosted CI credentials or production repositories are supplied.
Setup prerequisites
- Dependency graphs
- Process exit codes
- Test isolation
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- DCI-101 · Pin the required-check contract before optimizing the pipeline
- DCI-103 · Compute affected packages from both dependency directions
- DCI-104 · Key build caches from every semantic input
- DCI-102 · Fail the pipeline when a command exits through a hidden pipe
- DCI-105 · Cancel superseded pull-request runs without erasing evidence
Acceptance criteria
- Record created, queued, started, and completed timestamps
- Report queue, setup, execution, and artifact phases separately
- Percentiles retain workload and executor-class dimensions only
Implementation constraints
- Use bounded synthetic dimensions and state the observation window.
Verification to include
- Reconcile phase durations for a mixed local workload.
- Omit a timestamp and confirm the run is marked incomplete rather than assigned zero delay.
Deliverables
- CI latency model and workload report
Rollout and recovery
Use the baseline before changing runner count or job structure.
Value of the work
For the engineer: Practice treating CI as a versioned delivery system with correctness, latency, and recovery constraints.
For the team: Review a pipeline that reduces wasted compute without allowing stale or skipped checks to approve changes.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.