> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/introduction-to-ci-cd/bitbucket-pipelines.md). # Bitbucket Pipelines CI/CD using Bitbucket Pipelines Bitbucket Pipelines is a continuous integration and delivery (CI/CD) service built into Bitbucket, Atlassian's Git-based version control system. Pipelines allow developers to automatically build, test, and deploy their code every time they push changes to a Bitbucket repository. Here are some key features of Bitbucket Pipelines: * **Easy setup**: Pipelines are built into Bitbucket, so it's easy to get started with no additional setup. * **Flexible configuration**: Pipelines can be configured using YAML files, allowing for high customization. * **Docker support**: Pipelines uses Docker containers to provide a consistent and isolated environment for running builds and tests. * **Parallel builds**: Pipelines can run multiple builds in parallel, which can help speed up the overall build process. * **Deployment options**: Pipelines can deploy your code to various platforms, including AWS, Google Cloud, and Azure. --- # 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.duplocloud.com/docs/automation-platform/introduction-to-ci-cd/bitbucket-pipelines.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.