# Automate with CI/CD

Build, test, and deploy on every push: with Acquia Pipelines or from your own CI provider. The [quickstart](/cloud-platform/ci-cd/quickstart/) runs your first Pipelines build.

Deploying a [Front End Hosting](/start-here/glossary/#front-end-hosting) frontend instead is a different flow: [deploy from your own CI/CD](/source-cms/deploy/external-ci/). A Drupal application can also [build its artifact in your own CI](/source-cms/deploy/external-ci/#deploying-a-drupal-application-this-way), the alternative to Pipelines.

- [Quickstart](/cloud-platform/ci-cd/quickstart/): Write a minimal acquia-pipelines.yaml, start a Pipelines job, and watch it build your Drupal application into a deployable artifact branch.
- [CI/CD on Acquia](/cloud-platform/ci-cd/guide/): The CI/CD surfaces (Pipelines for Cloud Platform work; your own CI or Code Studio for Front End Hosting), plus secrets, environment promotion, and team governance patterns that apply to any of them.