CI/CD & DevOps / Scenario

Boss: The Pipeline Autopsy

One workflow file, five buried landmines: a gate that gates nothing, evidence that self-destructs, mutable actions, and a retry loop with amnesia.

Difficulty
Boss
Format
Scenario
Points
300
Estimate
18 min

// MISSION BRIEF

Your Mission

You inherit the release pipeline of a team whose last three regressions "passed CI". The entire truth is in one YAML file. Read it like a hostile auditor: find why green means nothing, why failures leave no evidence, and what a defensible rewrite looks like.

Scoring: boss fight. Five weighted decisions; the gate-integrity call counts double.

// FIRST CONTACT

Battle teaser

First artifact

.github/workflows/release-tests.yml

Three regressions merged green. The line that broke the gate:

  1. Acontinue-on-error: true on the E2E step: the job succeeds even when the suite fails, so the required check approves anything
  2. Bnpm ci reinstalls dependencies each run
  3. Cruns-on: ubuntu-latest is too unstable for E2E
  4. Don: pull_request should be on: push
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

ci-cdpipeline-reviewgithub-actionsflaky-tests