CI/CD (Continuous Integration and Delivery)

CI/CD stands for Continuous Integration and Continuous Delivery (or Deployment). CI merges developers' changes frequently and runs an automated build and tests on each one. CD extends this by automatically preparing, and often deploying, every passing change to staging or production.

Why it matters

Automated pipelines catch breakage within minutes, not days, and make releases routine rather than risky events. Small, frequent deployments are easier to debug and roll back. The risk is that a fast pipeline can also ship a bad change quickly, so monitoring after each deploy matters.

Example

A pipeline defined in YAML:

on: [push]
jobs:
  test:
    steps:
      - run: npm ci
      - run: npm test
  deploy:
    needs: test
    steps:
      - run: ./deploy.sh

Every push runs the tests; only if they pass does the deploy job run.

Common mistakes

Skipping or ignoring failing tests to get a release out.
Having no health check or rollback plan after an automated deploy.
Storing secrets in the pipeline file instead of the platform's secret store.

Get notified when this term updates

Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.