Home

/

Glossary

/

Infrastructure

/

CI/CD

Infrastructure

3 min read

What is CI/CD?

CI/CD (Continuous Integration/Continuous Delivery) is a software development practice that automates code building, testing, and deployment, enabling teams to release updates frequently and reliably through an automated pipeline.

What is CI/CD?

CI/CD stands for Continuous Integration and Continuous Delivery (or Continuous Deployment). It is a set of practices and tools that automate the process of integrating code changes, running tests, and deploying software to production environments.

  • Continuous Integration (CI) — Developers merge code changes to a shared repository frequently (multiple times per day). Each merge triggers automated builds and tests to catch integration issues early.
  • Continuous Delivery (CD) — Every code change that passes automated testing is automatically prepared for release to production. A human manually approves the final deployment.
  • Continuous Deployment — Goes one step further: every change that passes tests is automatically deployed to production with no manual approval.

    • The CI/CD Pipeline

    A typical CI/CD pipeline consists of stages:

  • Source — Code is committed to a version control system (Git).
  • Build — The application is compiled, bundled, or containerized.
  • Test — Automated tests run: unit tests, integration tests, end-to-end tests, security scans.
  • Deploy to staging — The build is deployed to a staging environment for final verification.
  • Deploy to production — After approval (or automatically), the build is released to production.

    • CI/CD and Automation Workflows

    CI/CD principles apply beyond traditional software development. Workflow automation benefits from the same ideas: version-controlled workflow definitions, automated testing of workflows before deployment, staged rollouts, and automated rollback when a workflow change introduces failures.

    Popular CI/CD Tools

    Common CI/CD platforms include GitHub Actions, GitLab CI/CD, Jenkins, CircleCI, Travis CI, and AWS CodePipeline. Container orchestration tools like Kubernetes and Docker Compose are frequently used in the deployment stages.

    CI/CD automates the build, test, and deployment pipeline, a core DevOps practice documented by Google Cloud. Autonoly complements these pipelines by automating operational steps through its SSH terminal and API & HTTP features.

    Why It Matters

    CI/CD practices ensure that automation workflows and their underlying infrastructure are tested and deployed reliably. Understanding CI/CD helps teams manage workflow versioning, test changes before they affect production data, and roll back quickly when issues arise.

    How Autonoly Solves It

    Autonoly provides a managed execution environment where workflows run in isolated containers. You do not need to set up CI/CD pipelines for your automations — the platform handles versioning, execution isolation, and rollback. For teams that integrate Autonoly into their development pipeline, the REST API enables triggering workflows from CI/CD systems.

    Learn more

    Examples

    • A GitHub Actions pipeline that runs end-to-end tests against a staging API, then triggers an Autonoly workflow to update production data if all tests pass.

    • A deployment pipeline that uses containerized builds to ensure the same environment runs in development, testing, and production.

    • A workflow versioning system where changes to automation logic are tested against sample data before being promoted to the production schedule.

    Frequently Asked Questions

    Continuous delivery automates everything up to production deployment but requires a manual approval step before releasing. Continuous deployment removes that manual gate — every change that passes automated tests is deployed to production automatically. Continuous deployment requires higher confidence in your test suite.

    If you are using a managed platform like Autonoly, the platform handles execution and deployment for you. However, if you build custom automation scripts or integrate workflows into a larger software system, CI/CD ensures changes are tested and deployed reliably without breaking existing automations.

    You might also like

    Blog Posts
    Use Cases
    ← CAPTCHACloud Computing →

    Related terms, automations and guides

    Where this concept shows up in practice.

    DefinitionContainerizationContainerization is a technology that packages an application and all its dependencies into a lightweight, isolated unit called a container, ensuring it runs consistently across any environment without conflicts.DefinitionWorkflow AutomationWorkflow automation is the use of software to execute recurring business processes with minimal human intervention, routing tasks, data, and decisions through a predefined sequence of steps.DefinitionError HandlingError handling is the practice of anticipating, detecting, and responding to errors in software execution, including catching exceptions, logging failures, and implementing fallback logic to keep automated workflows running reliably.DefinitionTask SchedulingTask scheduling is the process of automating when and how tasks execute, whether on a fixed timetable, triggered by events, or managed through a dependency-aware queue that ensures tasks run in the correct order.DefinitionREST APIA REST API is a web service interface that follows Representational State Transfer (REST) architectural principles, using standard HTTP methods to create, read, update, and delete resources. It is the most widely adopted API style for web and mobile applications.DefinitionAPI Rate LimitAn API rate limit is a restriction on the maximum number of API requests a client can make within a defined time window. Rate limits protect servers from overload, ensure fair resource distribution among users, and prevent abuse of API services.DefinitionDevOpsDevOps is a set of practices, cultural philosophies, and tools that unify software development (Dev) and IT operations (Ops) to shorten the development lifecycle and deliver high-quality software continuously. It emphasizes automation, collaboration, monitoring, and rapid iteration.DefinitionHTTPHTTP (Hypertext Transfer Protocol) is the foundational protocol of the web that defines how clients and servers communicate. Every API call, web page load, and webhook delivery travels over HTTP.

    Stop reading about automation.

    Start automating.

    Describe what you need in plain English. Autonoly's AI agent builds and runs the automation for you — no code required.

    See Features