back to labs
GitHub Actions: The Job That Ran Too Early
MediumDevOps10-15 minThe brief
A production pipeline 'succeeded' but shipped nothing: a job ran in parallel with the jobs it should have waited for, because it has no needs: dependency. Examine /root/project/ci.yml (job names differ per session). The first (root) job correctly needs nothing, but one DOWNSTREAM job has no active needs: at all — a commented-out needs line doesn't count. Record that job's name to /root/answers/job.txt.
What you'll do
- Record the downstream job with no needs: to /root/answers/job.txt
Hands-on lab: you work on a real Linux box in your browser, graded on the machine's actual state.
