Pipelines helps you to integrate applications on your Cloud Platform CD environments with version control repositories hosted by Bitbucket.

To connect your regular Cloud Platform environments with Bitbucket, visit Using Cloud Platform with a remote repository

Important considerations

• Pipelines cannot be connected to newly-created Bitbucket accounts because of the following reasons:
  • Bitbucket no longer supports default workspaces.
  • Pipelines does not support custom workspaces.
• Pipelines can be connected only to repositories owned by the current Bitbucket user.
• This feature works only with Bitbucket Cloud and not with Bitbucket Server.
• Only account owners can connect to repositories created under the default workspace of the Bitbucket account.
• The workspace ID is a part of the URL of the repository, and the default workspace has the same name as the user name.

For more issues, see Known issues and Known issues in Cloud Platform CD.

Requirements

Before you connect a CD environment to your repository, ensure you meet the requirements for your repository, based on the following:

• If you don’t have a Bitbucket repository, sign in to your Bitbucket account, and then visit bitbucket.org/repo/create to create a new repository from the Bitbucket UI.

• If you have an existing repository, add Bitbucket as a new remote by modifying your project repository’s local clone with the following code (where [username] is your Bitbucket username and [project] is the name of your project):

  copy

  git remote add bitbucket [email protected]:[username]/[project].git
  git push bitbucket master

Procedure

To use the Cloud Platform interface to connect an application on a CD environment with your Bitbucket repository:

1. Sign in to the Cloud Platform user interface.
2. Click the name of the application you want to connect to Bitbucket.
3. In the left menu, click Pipelines. If your application doesn’t display a Pipelines link, contact Acquia Support.
4. Select More links > View Application Info.

5. In the Connected repository information section, click the Configure link. A configured Git email address is required. If the email address is invalid, Pipelines jobs won’t start when changes are pushed, and webhooks will fail with HTTP 500 errors.

   

6. In the Select Source section, click the Choose source link.

   

7. Click the Configure link for the Configure Pipelines with your Bitbucket repository section.

   

8. Click Connect to Bitbucket. Pipelines will connect to Bitbucket and display a confirmation page.
9. Click the Grant access button in the Bitbucket interface to grant your application access to your Bitbucket repository. The Cloud Platform interface for your environment’s pipelines information will be displayed.

Each time you use Bitbucket to create or reopen a pull request or push a commit, Cloud Platform executes the pipelines start command using the build definition file in the Bitbucket repository, and commits the resulting build artifact, named pipelines-build-[BRANCHNAME], to your Cloud Platform repository.

Next step

To operate, Pipelines expects a file in YAML format named acquia-pipelines.yaml to exist in the root directory of your code repository. This build definition file has all the information required for Pipelines to perform the build, including any variables required and the instructions used to perform the build. Pipelines can build from both forked and non-forked repositories.

For information about how to structure the file and what it should contain, see Creating and managing your build definition file.

Connecting Pipelines to your Bitbucket repo

Procedure

To use the Cloud Platform interface to connect an application on a CD environment with your Bitbucket repository:

1. Sign in to the Cloud Platform user interface.
2. Click the name of the application you want to connect to Bitbucket.
3. In the left menu, click Pipelines. If your application doesn’t display a Pipelines link, contact Acquia Support.
4. Select More links > View Application Info.

5. In the Connected repository information section, click the Configure link. A configured Git email address is required. If the email address is invalid, Pipelines jobs won’t start when changes are pushed, and webhooks will fail with HTTP 500 errors.

   

6. In the Select Source section, click the Choose source link.

   

7. Click the Configure link for the Configure Pipelines with your Bitbucket repository section.

   

8. Click Connect to Bitbucket. Pipelines will connect to Bitbucket and display a confirmation page.
9. Click the Grant access button in the Bitbucket interface to grant your application access to your Bitbucket repository. The Cloud Platform interface for your environment’s pipelines information will be displayed.
10. Click Select Bitbucket repository.
11. Select the repository to which you want to connect, and then click Continue.

Each time you use Bitbucket to create or reopen a pull request or push a commit, Cloud Platform executes the pipelines start command using the build definition file in the Bitbucket repository, and commits the resulting build artifact, named pipelines-build-[BRANCHNAME], to your Cloud Platform repository.

Next step

To operate, Pipelines expects a file in YAML format named acquia-pipelines.yaml to exist in the root directory of your code repository. This build definition file has all the information required for Pipelines to perform the build, including any variables required and the instructions used to perform the build. Pipelines can build from both forked and non-forked repositories.

For information about how to structure the file and what it should contain, see Creating and managing your build definition file.