DebugMidDevOpsAuto-graded
Patch a CI pipeline uploading broken artifacts
The pipeline reports success while producing the wrong output, so there is no error message to follow.A CI pipeline is silently uploading broken artifacts — it goes green, and what it publishes is wrong. The faults are in the workflow itself: how the cache is keyed, which conditionals gate which steps, and how a secret is referenced. Find them and make the pipeline only publish artifacts that genuinely passed.25 min
yaml
You're done when
- The cache is keyed so it cannot serve stale content for a changed dependency set.
- Artifact upload is gated on the tests actually passing.
- Publishing is gated on a tag rather than running on every push.
- The secret is referenced by its correct name, so the step is genuinely authenticated.
- The workflow verifies what it publishes, through a version or provenance check.
What it measures
GitHubReading Actions workflow semantics — caching, conditionals and secret references — and knowing where each goes wrong.
Debugging and profilingDiagnosing a pipeline whose failure mode is a green run with a bad output.
Release safetyEnsuring the gates between passing and publishing are real rather than decorative.
Your environment
Terminal + editorA full shell in the browser
Claude CodePre-authenticated, no key setup
Isolated microVMYours alone, wiped afterwards
Start this lab
25 min
Start labYou'll sign in to Anthropos to start. The lab opens in a private cloud workspace with Claude Code ready to use.AI Labs is part of Anthropos Workforce. Not on your plan yet? Book a demo