For many projects in nodeJS, we use to launch pipelines which make first a npm install, then a npm test and finally a docker build before to send the built package to GCP.
On my example, my app have a private dependency on a private repo on the same account.
We created a couple of ssh keys and added the public key on the dest repo so the npm install and the npm test work perfectly in the pipeline !
But when the pipeline try to lauch the buil (docker build), it starts correctly and the engine try to access to the external dependency (like the npm install...) and we got the error :
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://firstname.lastname@example.org/*****/********
npm ERR! Host key verification failed.
npm ERR! fatal: Could not read from remote repository.
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR! exited with error code: 128
This worked perfectly like this the last time we tried to build. But it seems that somethings changed...
We spent 1,5 day to try many different things but we always got the same error.
Please is there anybody who can help use ?
Are you still experiencing this issue?
It's a bit hard to debug this remotely. As a first step can you please try to generate a new key pair in the settings for Bitbucket Pipelines(Repo settings, then look under "Pipelines") in your Node repo. Then copy the public key and add it to the account settings of the repo you are trying to clone. There is an explanation how to do that here in Step 4.
I realise that you have probably already done that, but often these errors are a result of faulty copy+paste or something similar. If you are still having issues you can contact support for more help.
Thanks for your answer. We still experiencing this issue... And yes we already did exactly what you say. We don't have any problem when the pipeline just do a npm install and get the dependencies.
We have the problem only when the pipeline try to build the node project. In this config, it is not the pipeline which launch the npm install in its env but a new env with a new node pod launch by the dockerfile file...
In the dockerfile we try to manually add the private key to read the repo and we are enable to make a git clone from the fresh pod when the pipeline launch the build. So i think that our keys are good.
The problem, i think, is around the "Host key verification failed". So we tried to manually add the host fingerprint in the known_host file but we still have the error..
We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events