With the new SSH Keys Pipeline settings, i can easily get ssh access to my server from pipelines. Which is great.
I use http://pm2.keymetrics.io/docs/usage/deployment/ to deploy my JS code to my server. It logs into my server (which works because of the ssh keys), then pulls the git code from bitbucket, which doesn't work because it has no access. Sad panda :(
pm2 supports forward-agent, and this works from my local machine. I added the Pipelines ssh-key to my project, so it gets read access. Still no luck. Whe i debug the ssh connection to bitbucket, I can see
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/appuser/.ssh/id_rsa
etc. which is my server user.
Whilst running this locally, my server will return my local id and get a successfull connection with it.
So i can only imagine, forward-agent is not working. Any ideas?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot