supraj.dev
CI/CD and GitOps

CI pipelines

How does a bad code change get caught before users ever see it?

28 s loop7 sentencesSilent, read alongScene: Journey
Read the story, sentence by sentence 7 sentences

What you'll be able to say

  1. A CI (continuous integration) pipeline usually starts on each push to a Git repository, so every change gets checked the same way.
  2. The pipeline first builds the code, then runs automated tests such as unit tests that check small pieces of behaviour.
  3. If a test fails, the pipeline fails, and later stages like deployment normally don’t run, so the broken change doesn’t ship.