Build prompting for password


#1

I’m trying to wire up a Drupal site through BitBucket --> CircleCI --> Pantheon. I’m using the Pantheon drops-8-composer upstream and in the CircleCI configuration it includes, it is getting hung up in the “build_deploy_and_test” job under “prepare database for site-under test”.

The command where I believe it is getting stuck is:
terminus -n build:env:create “$TERMINUS_SITE.dev” “$TERMINUS_ENV” --yes -vvv --clone-content --notify="$NOTIFY"

I get in the CircleCI build:

#!/bin/bash -eo pipefail
./.circleci/scripts/pantheon/02-init-site-under-test-clone-existing
 [notice] OK >> dev-natural-alternative.pantheonsite.io responded
 [notice] Pushing code to ci-32 using branch ci-32.
 [notice] Running git -C /root/example_drops_8_composer remote add pantheon ssh://codeserver.dev.bc9f3f09-d097-445b-92b5-3d73f8ec236b@codeserver.dev.bc9f3f09-d097-445b-92b5-3d73f8ec236b.drush.in:2222/~/repository.git
 [notice] Set build-metadata.json to {"url":"git@bitbucket.org:naturalawn/natural-alternative.git","ref":"master","sha":"a1e8d3cd597c489c37e5475b0152184bbf15e668","comment":"CircleCI Testing 07","commit-date":"2018-05-03 21:12:47 -0400","build-date":"2018-05-04 01:14:10 +0000"}.
 [notice] Running git -C /root/example_drops_8_composer checkout -B ci-32
Switched to a new branch 'ci-32'
M	.gitignore
 [notice] Running git -C /root/example_drops_8_composer add --force -A .
 [notice] Running git -C /root/example_drops_8_composer commit -q -m 'Build assets for ci-32.'
 [notice] Running git -C /root/example_drops_8_composer push --force -q pantheon ci-32
Warning: Permanently added '[codeserver.dev.bc9f3f09-d097-445b-92b5-3d73f8ec236b.drush.in]:2222,[35.184.164.143]:2222' (RSA) to the list of known hosts.

codeserver.dev.bc9f3f09-d097-4@codeserver.dev.bc9f3f09-d097-445b-92b5-3d73f8ec236b.drush.in's password: 

At this point, it just sits and waits for a password. I think I have all the proper SSH keys set up, but I’m very new to CircleCI so I’m not 100% sure. Any suggestions would be most helpful.

Thanks!


#2

Is this step checking out some code? If so, did you add a user-key to your project so that it could have access to multiple repos?

We don’t support password based checkouts. I have never used this tool, but ultimately you need to get it to check out using SSH and you need to make sure that a valid checkout key exists in your project.


#3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.