All terms

CI/CD

Continuous Integration and Continuous Delivery — automating build, test, and deployment every time code changes.

DevOps1 min read

Definition

CI runs tests and linters on every push or pull request. CD promotes passing builds to staging or production automatically or with one click.

It catches bugs early and makes releases routine instead of risky big-bang deploys.

In simple terms

CI/CD is a quality checkpoint on an assembly line — every part is inspected before the next stage, not only at the final door.

Where you see it

  • GitHub Actions runs tests on Goobo Labs repos.
  • Teams deploy container images after green CI.

How it works

  1. 1.Trigger

    Push, PR, or schedule starts the pipeline.

  2. 2.Build and test

    Compile, unit test, lint, security scan.

  3. 3.Deploy

    Ship artifacts to servers or app stores if checks pass.

Why it matters

  • CI/CD is standard practice for reliable software and ML infrastructure.

Often confused

  • CI/CD means deploy to production on every commit automatically.

    Continuous Delivery may stop at staging; Continuous Deployment goes live automatically — teams choose their risk level.