Information for: DEVELOPERS   PARTNERS   SUPPORT

Known issues in Cloud Platform CD

This page describes known issues with Cloud Platform CD. For issues with Acquia Pipelines, see Known issues in Acquia Pipelines.

If you experience any difficulties with your Cloud Platform CD subscription, contact Acquia Support for help.

Known issues with Cloud Platform CD

Pipelines deploys to any environment with a

pipelines-build-artifact branch

Attempts to use Pipelines to copy databases to a specific environment will succeed even if that branch is deployed to a non-Cloud Platform CD environment, which may have unintended consequences.

Workaround: To prevent this behavior, wrap the pipelines-db-sync command in conditional logic, like the following example:

if [ ${PIPELINE_DEPLOY_VCS_PATH} != "pipelines-build-<branch>" ]; then echo "Syncing DB to destination." && pipelines-sync-dbs <databases>; else echo "On the master branch. Skipping DB Sync."; fi

When creating a new Cloud Platform CD environment, the post-code-deploy hook is

not run

When Cloud Platform creates a new Cloud Platform CD environment and deploys code to it, the post-code-deploy cloud hook is not run.

Workaround: To import configuration on a new Cloud Platform CD environment, perform a second deployment to the new environment.

Multiple CD environments created through Pipelines when you create a branch and

pull request on a connected repository

Pipelines runs jobs whenever you create new branches or open pull requests on the connected repository. Most subscribers with GitHub or Bitbucket as the connected repository use a workflow where pull requests are opened from feature branches on forked repositories. It implies that pipelines jobs don’t run against feature branches. However, if you instead create branches on the connected repository and then open pull requests from those feature branches, you will get a Pipelines job for both the feature branch and the pull request. Since each Pipelines job calls pipelines-deploy, you will get a CDE for each job (two CDEs total).

Workaround:

  • In the connected repository (GitHub/Bitbucket), modify the webhook settings for Pipelines on the connected repository and disable either the “push” or “pull request” webhook depending on your preferred workflow, so that Pipelines only runs jobs for the enabled webhook type.
  • In acquia-pipelines.yaml, replace pipelines-deploy with code similar to the following to selectively run pipelines-deploy only on specific types of builds:
if [[ ${PIPELINE_DEPLOY_VCS_PATH} == pipelines-build-pr* ]]; then echo "Creating CD environment for PR." && pipelines-deploy; else echo "Not a PR. Skipping CD environment creation."; fi