Pipelines FAQ¶

Why cannot I manually start jobs on tags?¶

Manually starting jobs only works with branches. Tags are not supported. To manually start a job, ensure that you do it from a branch instead.

Why is my job not triggered automatically?¶

When both branches and tags do not trigger your pipelines jobs automatically, then it might indicate we need to reset your pipelines credentials.

Contact Acquia support to request your pipelines credentials to be reset.

Why cannot I use RVM?¶

If your YAML build definition invokes rvm (Ruby Version Manager), you will run into errors. To work around the issue, you need to switch your build to using rbenv instead. Rbenv is a lightweight and more developer-friendly option to switch between Ruby versions.

To continue using different versions of Ruby, replace any instances of rvm in your YAML build definition with equivalent rbenv commands.

• rvm install x.x.x becomes rbenv install x.x.x.
• rvm use x.x.x becomes rbenv global x.x.x or rbenv local x.x.x depending on the desired behavior.

Why am I getting a Webhook creation failed error when trying to connect my Bitbucket repository?¶

When connecting your Bitbucket repository with Acquia Pipelines, you might run into the following error:

Danger! 400 : {"success":false,"message":"Webhook creation failed for app [\"ff312a79-a73b-4d51-b770-f298292907db\"], repo mybitbucketnamespace/mybitbucketrepo,
reason: User unauthorized to create deployment key","error":"Webhook creation failed for app [\"ff312a79-a73b-4d51-b770-f298292907db\"], repo mybitbucketnamespace/mybitbucketrepo,
reason: User unauthorized to create deployment key"}

This is a known limitation with the Bitbucket service. Only account owners can connect to repositories created under the default workspace of the Bitbucket account.