Continuous Integration and the Build Pipeline · seed 1 · A4, ink-friendly. The answer key prints on its own page for grown-ups.

A machine that says ready

Computing · Software Engineering · ages 20-22
Name ______________________   Date ____________

  1. In which order does a change move through the pipeline?

    • Merge, push, build, test
    • Test, merge, push, build
    • Push, build, test, merge

  2. What runs on a clean machine for every pushed change?

    • A backup of each laptop
    • The build and the test suite
    • The release party playlist

  3. Nothing counts as done until the pipeline agrees.

    Circle one:   True   False

  4. The pipeline takes an hour. What does the team lose?

    • All test coverage, since tests stop running
    • Fast feedback, so changes arrive in big slow batches
    • The ability to push code at all

  5. Your change passes on your laptop but fails in the pipeline because of a missing file. Why is that failure useful?

    • It exposes a dependence on your local setup
    • It proves pipelines are always wrong
    • It shows the tests are too strict

  6. The pipeline is red. What should the team do first?

    • Keep pushing and fix it on Friday
    • Delete the failing stage
    • Fix the pipeline before new work

  7. A developer says a pipeline failure is meaningless because the code works on their laptop. What is the flaw?

    • Laptops are always faster than servers
    • Shipping means running beyond one laptop, so the clean machine is the honest judge
    • Pipelines never test real behaviour

  8. Two teams have identical tests. Team A gets signal in five minutes, team B in ninety. How will their habits differ after a month?

    • Team B will batch bigger and debug less often
    • Team B will push small changes more often
    • Both teams will behave exactly the same
LightMySky · lightmysky.comW1-mt_z__G4nfjwh-s1

Answer key

For grown-ups. Fold this page away before handing over the rest.

A machine that says ready W1-mt_z__G4nfjwh-s1

  1. Push, build, test, merge · Push starts it, build and test check it, merge finishes it.
  2. The build and the test suite · Every change is rebuilt and retested where no local setup can hide faults.
  3. True · The pipeline is the team's shared definition of ready.
  4. Fast feedback, so changes arrive in big slow batches · Slow signals mean fewer runs, bigger batches, and late news.
  5. It exposes a dependence on your local setup · The clean machine reveals what your laptop silently provided.
  6. Fix the pipeline before new work · Every merge waits on the pipeline, so a red one blocks everything.
  7. Shipping means running beyond one laptop, so the clean machine is the honest judge · Working on one laptop is not the bar. The shared machine decides.
  8. Team B will batch bigger and debug less often · Slow feedback trains people to run the pipeline rarely and in bulk.
Worksheet · LightMySky