Information for: DEVELOPERS   PARTNERS

Managing your pipelines in the Acquia Cloud interface

The Acquia Cloud pipelines feature is available as an add-on for Acquia Cloud Enterprise subscribers. To obtain this feature for your subscription, contact your Account Manager.

Acquia Cloud provides you the ability to start and track your different pipeline jobs with both an application in the user interface and a command-line interface.

Accessing the pipelines user interface

Subscribers using IP address whitelisting must use pipelines from the command line, instead of the user interface. For more information, see this known issue.

To view information about your pipelines in Acquia Cloud, complete the following steps:

  1. Sign in to Acquia Cloud with an account that has the Execute pipelines permission.
  2. Select the application that you want to use.
  3. In the left menu, click Pipelines.

The first time you visit the page, you can select from one of the following options:

  • Select a source for your repository
  • Start a pipeline job
  • View the available environments

Follow-on visits to the page (after you have configured your repository connection) will display a list of the logged pipeline jobs.

Managing your repository connection

Acquia Cloud displays information about your repository connection, including its URL and several common Git commands. To examine or change your the repository connected to your application, on the Pipelines page click More Links.

More Links icon

You can then click View Connection Info, which allows you to change to a different repository for your application. To do this, click the Configure link, select the type of repository that you want to use, and then complete its configuration based on your repository. For information about using this process to connect to external code repositories, see Connecting an application to an external Git repo.


Acquia Cloud subscribers with Node.js applications that were developed in an Acquia-hosted Git repository can use webhooks to create build artifacts on commit. Although Drupal-based applications are incompatible with webhooks for deployment, Drupal-based applications can use webhooks for non-deployment continuous integration tasks, such as linting and testing.

To prevent the execution of code that results in an infinite loop, Acquia Cloud disables webhooks used to trigger pipelines jobs on Git repositories hosted by Acquia. Learn more.

To enable or disable a webhook in the Acquia Cloud user interface, complete the following steps:

  1. Sign in to Acquia Cloud.
  2. Select an application.
  3. Click Pipelines.
  4. Click More links > View Application Info.
  5. In the Webhooks section, click Enable or Disable as required.

Acquia Cloud will display a confirmation dialog box in the upper right of the webpage.

Reviewing job activity

The Job List page for Acquia Cloud provides an overview of the pipeline jobs that are both currently processing or have already completed. The webpage will regularly update to include any new jobs, or to reflect the status of any on-going or newly completed jobs. To learn more about the overview page, see Viewing pipelines job history.

Detailed information about any job listed on the Job List page can be found by clicking on the job’s name in in the Job column. To learn more about reading detailed job information, see Viewing job output.

Starting a pipeline job

To start a new pipeline job from the Acquia Cloud interface, complete the following steps:

  1. Select the application for which you want to start a pipelines job.

  2. In the left menu, click Pipelines.

  3. Click Start Job.

    Start Job icon

    Acquia Cloud will display a How to start a job dialog.

  4. In the Branch Name field, enter the name of the branch that contains the build definition file that you want to use.

  5. Click Start.

You may execute a maximum of two jobs at one time.


The pipelines feature executes subsequent jobs using the credentials of the user who first executes a pipelines build. For more information on how to update to another user, see User permission issues.