I am having issues with doing deploys (from the Roots Trellis deploy script) from a Bitbucket Pipeline to a staging/prod server. The problem specifically is:
TASK [deploy : Clone project files] ********************************************
System info:
Ansible 2.8.8; Linux
Trellis Head
---------------------------------------------------
fatal: [46.101.65.29]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
...ignoring
TASK [deploy : Remove untracked files from project folder] *********************
ok: [46.101.65.29]
TASK [deploy : Failed connection to remote repo] *******************************
System info:
Ansible 2.8.8; Linux
Trellis Head
---------------------------------------------------
Git repo git@bitbucket.org:clayton93/trellis.git cannot be accessed. Please
verify the repository exists and you have SSH forwarding set up correctly.
More info:
> https://roots.io/trellis/docs/deploys/#ssh-keys
> https://roots.io/trellis/docs/ssh-keys/#cloning-remote-repo-using-ssh-
agent-forwarding
fatal: [46.101.65.29]: FAILED! => {"changed": false}
It seems to be having trouble cloning the repo. The repo is the same (private) repo the Pipeline is running in. I have added the pipeline’s SSH key to the repo’s Access Keys which I hoped would solve it.
My pipeline config is:
pipelines:
branches:
master:
- step:
name: First Step
image: misterio92/ci-php-node:3.0
caches:
- composer-bedrock
- composer-sage
- node-sage
script:
- cd $BITBUCKET_CLONE_DIR/trellis && echo $VAULT_PASS > .vault_pass
- apt-get update -qy
- apt-get install -y python-dev python-pip
- chmod 700 /opt/atlassian/pipelines/agent/build
- chmod 700 /opt/atlassian/pipelines/agent/build/trellis
- cd $BITBUCKET_CLONE_DIR/trellis && pip install -r requirements.txt
- cd $BITBUCKET_CLONE_DIR/trellis && ansible-galaxy install -r galaxy.yml
- cd $BITBUCKET_CLONE_DIR/trellis && ./bin/deploy.sh production trellis.wearefx.uk --vault-password-file .vault_pass --inventory hosts/production
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.