Fail the pipeline when a command exits through a hidden pipe
Test output is piped through a formatter; the formatter succeeds after the test process fails, so the job reports green.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Shell behavior · Process status
Estimated field mix
- DevOps70%
- Quality 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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Job status reflects every command in the pipeline
- Original stdout and stderr remain available
- Signal termination and ordinary nonzero exit are distinguished
Implementation constraints
- Do not parse human-readable output to determine success.
Verification to include
- Run successful tests through the formatter and retain readable logs.
- Fail the upstream process and verify the job reports its exact failure.
Deliverables
- Exit-status wrapper and pipeline regression
Rollout and recovery
Apply first to test jobs, then audit every piped command.
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.