grceng.academy
Triage lab 40 bonus XP

Triage the pipeline gate report

Start labRead the room

Objectives

Eight production deployments went out yesterday. The control gate is configured but the report shows it was not always the deciding factor.

Raise the deployments where the gate did not actually control the release. Leave the ones where it did.

List only the lines that qualify, worst first. Severity is one of: critical | high | medium | low. Add or delete rows as needed.

Deployment gate report

V-1  Deploy 4471: gate skipped: the job's continue-on-error is true, so a failed policy check did not block the release.
V-2  Deploy 4472: gate passed, all checks green.
V-3  Deploy 4473: released from a local machine, bypassing the pipeline entirely.
V-4  Deploy 4474: gate failed, release blocked, fixed and redeployed.
V-5  Deploy 4475: gate passed after an engineer edited the workflow in the same PR to remove two checks.
V-6  Deploy 4476: gate took 11 minutes, longer than the 5-minute target.
V-7  Deploy 4477: gate passed; evidence artefact retained 90 days.
V-8  Deploy 4478: gate ran after the deploy step rather than before it.

Checks the server runs (4)

  • The right findings are raised
  • Benign lines are left out
  • Severity matches the actual exposure
  • Ranked worst first

Check names are all you see here: the expectations that decide pass or fail, and the reference solution, stay on the server.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

  1. Step 1

    Read the fixture as a population, not a list

    A gate is a control only when a failure prevents the release. Read each deployment and ask what would have happened had the checks failed.

  2. Step 2

    Decide what actually qualifies

    Four deployments were not actually gated: one swallowed the failure, one skipped the pipeline, one shrank the checks in the same change, and one ran the gate too late to matter.

    The right findings are raised

  3. Step 3

    Resist the loud lines

    Slow gates and retained artefacts are operational facts. The blocked deploy is a success story, including it dilutes your list.

    Benign lines are left out

  4. Step 4

    Grade the exposure, not the wording

    Rank the total bypass highest: a release that never touched the pipeline has no control coverage at all.

    Then the swallowed failure, which produces a green record of a failed check; then the self-service weakening of the checks; then the ordering defect, which at least leaves a truthful record.

    Severity matches the actual exposure

  5. Step 5

    Rank so the first line is the one you act on

    Worst first is the deployment for which you have the least assurance, not the one with the most alarming label.

    Ranked worst first

Rules summary

  • XP on pass

    40 bonus XP the first time every check goes green.

  • Paid hints

    2 available. Each costs 25% of the lab XP (about 10 XP).

  • Reveal solution

    Scores 0 XP and unlocks only after 3 check runs.

  • Attempt cap

    60 check runs per learner. The runner warns you in the last 10.

  • Drafts

    Your editor content is saved in this browser, so a reload will not lose work.

  • Walkthrough

    Always free and never penalised: use it before spending a hint.