Skip to content

CI/CD

The software development lifecycle is made simpler by a set of protocols known as Continuous Integration/Continuous Deployment (CI/CD).

CI/CD is an essential part of the software development lifecycle, assisting teams in responding to market needs and effectively delivering high-quality software. Before Continuous Integration and Continuous Delivery, the software development process was characterized by long development cycles, high error rates, and inconsistent releases. CI/CD is now widely accepted as best practice among teams for quickly releasing changes, automating testing, and merging code conveniently.

Your code modifications can be combined with CI into a single repository for testing and CI. CI produces more dependable and resilient code by assisting in the early detection of integration problems. Conversely, Continuous Deployment (CD) automates the release of code to production after it has passed many automated tests, guaranteeing that new features and bug fixes reach end users promptly and reliably.

Startpunten

  • What is CI/CD?
  • [SonarCube] https://www.sonarsource.com/products/sonarqube/
  • [Policy checking with Terraform] https://oneuptime.com/blog/post/2026-02-23-terraform-cicd-policy-checks/view

Key Points

  • version control on terraform scripts in a pipeline is mandatory
  • checks on policies, mis configurations etc. should be implemented
  • whether or not to use Sonarcube as optional tool could be investigated