> 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) 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` 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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.