# CICD Intro A CI/CD Pipeline is simply a development practice. It tries to answer this one question: *How can we ship quality features to our production environment faster?*

src: https://www.freecodecamp.org/

Without the CI/CD Pipeline, the developer will manually perform each step in the diagram above. To build the source code, someone on your team has to run the command to initiate the build process manually. **Continuous Integration (CI)** Automatically tests code changes in a shared repository. Ensures that new code changes don't break the existing code. **Continuous Delivery (CD)** Automatically deploys all code changes to a testing or staging environment after the build stage, then manually deploys them to production. **Continuous Deployment** This happens when an update in the UAT environment is automatically deployed to the production environment as an official release.

src: https://www.freecodecamp.org/

--- # Agent Instructions: 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: ``` GET https://gchandra.gitbook.io/big-data-and-tools-with-nosql/tools/cicd-intro.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.