> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/c/ci-cd-continuous-integration-continuous-deployment.md). # CI/CD (Continuous Integration/Continuous Deployment) A method to frequently deliver apps to customers by introducing automation into the stages of app development. CI/CD combines Continuous Integration and Continuous Deployment (or Continuous Delivery) into a unified set of practices for automating the software delivery pipeline. Continuous Integration involves automatically building and testing code changes as they are merged into a shared repository. Continuous Deployment extends this by automatically releasing validated changes to production. A typical CI/CD pipeline includes stages for code compilation, unit testing, integration testing, security scanning, and deployment. Tools like GitHub Actions, GitLab CI, Jenkins, and CircleCI orchestrate these stages. The goal is to reduce the time between writing code and delivering it to users while maintaining quality through automated checks. In serverless and API gateway environments, CI/CD is essential for managing configuration-as-code deployments. API gateway routing rules, rate limiting policies, and authentication settings can be version-controlled and deployed through the same pipeline as application code. This ensures that infrastructure changes are reviewed, tested, and auditable. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/c/ci-cd-continuous-integration-continuous-deployment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.