Stop 06 · CI/CD PipelinesTopics · 9/10

Pipeline as Code

Part of the DevOps Roadmap

In short

Defining your CI/CD pipeline itself in a version-controlled file (Jenkinsfile, .github/workflows, .gitlab-ci.yml) rather than configuring it manually through a UI — applying the same discipline from Phase 4 to pipeline configuration.

How to learn this

  1. 1Convert a manually-configured pipeline step into a version-controlled config file if you have one.
  2. 2Learn why pipeline changes going through pull request review catches mistakes before they break builds.
  3. 3Understand this is the same 'everything as code' philosophy that extends into Phase 9's infrastructure as code.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge