Acquia CMS

CI/CD delivery pipeline

Acquia CMS uses Travis for CI pipeline and ORCA as backend for CD pipeline.

  • For CI, jobs can be scheduled in travis.yml.
  • For CD, jobs can be scheduled in acquia-pipeline.yml.

The following workflow explains how Acquia CMS handles configuration for existing and new customers:

Travis CI

Travis CI is a continuous integration service that offers tight integration into Github.

Travis CI:

  • Helps project owners to have automated tests run against any proposed code changes when a pull request is created.
  • Gives a pass/fail rating to the code change and helps to reduce human errors such as typos and code formatting issues.
  • Tests the functionality of the project.


Official Representative Customer Application (ORCA) is a tool for collectively testing all software packages of a company in the context of a realistic, functional, best practices Drupal build. ORCA automatically runs Nightwatch tests in the SUT tagged with the package’s machine name.

Acquia Code Studio

Acquia has partnered with GitLab to offer Code Studio, a complete DevOps platform integrated with Cloud Platform that is optimized for Drupal development. Acquia hosts and manages Code Studio (GitLab) within Cloud Platform on our Next generation infrastructure.

For applications hosted on Cloud Platform, Code Studio provides pre-built automation to support low-configuration, continuous integration, and continuous delivery of projects built on the current Drupal version. You can extend and customize the default pipeline configuration based on your needs.

For more information about Code Studio, see Code Studio.

Acquia Pipelines

Acquia Pipelines is a continuous delivery tool to automate development workflows for applications hosted by Cloud Platform.

With Pipelines, you can:

  • Manage your application’s source code on a third-party Git infrastructure, and seamlessly deploy to Cloud Platform.
  • Use tools like Composer or drush make to assemble your application’s components and dependencies.
  • Use technologies such as Sass and TypeScript to compile application source code.
  • Control developers or teams that have permissions to change different parts of your application code base.

For more information about Pipelines, see Pipelines.