Acquia Pipelines is a tool for developing, testing, and deploying websites or other applications to Acquia Cloud. It enables you to:
- Manage your application's source code on GitHub, or other third-party Git servers, and seamlessly deploy to Acquia Cloud.
- Use tools like Composer or Drush Make to assemble your application's components and dependencies automatically.
- Use technologies like Sass and Typescript to compile application source code.
- Control which developers or teams have access to change different parts of your application code base.
Why use Acquia Pipelines?
Code that is built frequently needs consistency to achieve continuous integration. It can be a challenge for individual developers on a team to achieve consistency. In traditional deployment workflows, you need to do all of the work of assembling a website's deployment image in your code repository. Any resources (including Drupal core, contributed, or custom modules, or other code) must be copied into your code repository. If a module is updated, you will have to copy the new version of that module into your repository.
Using Acquia Pipelines, your workspace can contain just your website's version-controlled build instructions and private resources. You can keep the canonical version of external resources outside of your repository, and pull in the latest or other required version as you build your website for deployment.
How Acquia Pipelines works
Acquia Pipelines executes instructions that you provide to transform application source code into a build artifact which can then be tested and deployed. Specifically:
- Acquia Pipelines jobs are triggered when you run the Acquia Pipelines command line client's
pipelines startcommand or, optionally, by a commit or pull request at GitHub.
- Acquia Pipelines clones the Git source repository and checks out the specified branch. Initially, the source repository for your application is its Acquia Cloud Git repository, but you can choose to use a GitHub repository as the source using the
pipelines init-githubcommand. See Using GitHub with Acquia Pipelines.
- Acquia Pipelines looks for a file named
/acquia-pipelines.ymlin YAML format in the selected Git branch and executes the instructions it finds there. These instructions can assemble your application from multiple code bases, transform source files into compiled files ready to deploy, run tests, and so forth. See Using a build definition file.
- If all of the instructions in the YAML build defintion file succeed, Acquia Pipelines commits all of the files and directories created by the instructions as a build artifact to a build branch in the target repository. Currently, the target repository is always the application's Acquia Cloud Git repository.
- You can see the results of each job with the
logscommands. For jobs triggered by a GitHub pull request, you can also see the status posted in GitHub on the pull request.
Tutorials and examples
In addition to this product documentation, you can learn more about how to use Acquia Pipelines in the tutorials and example code at GitHub.