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):
Click the name of the application you want to connect to Bitbucket.
In the left menu, click Pipelines. If your application doesn’t display a Pipelines link, contact Acquia Support.
Select More links > View Application Info.
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.
In the Select Source section, click the Choose source link.
Click the Configure link for the Configure Pipelines with your Bitbucket repository section.
Click Connect to Bitbucket. Pipelines will connect to Bitbucket and display a confirmation page.
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 pipelinesstart 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.
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):
Click the name of the application you want to connect to Bitbucket.
In the left menu, click Pipelines. If your application doesn’t display a Pipelines link, contact Acquia Support.
Select More links > View Application Info.
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.
In the Select Source section, click the Choose source link.
Click the Configure link for the Configure Pipelines with your Bitbucket repository section.
Click Connect to Bitbucket. Pipelines will connect to Bitbucket and display a confirmation page.
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 pipelinesstart 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.
Cloud Platform