I've spent hours trying to get this to work; I would have hoped that this would work out of the box. Plus it sure would have helped to have the login/SSH information available on the main index page.
Anyhow, after launching an instance with the BitNami Jenkins stack, I couldn't get it to work with Publish over SSH. Instead I did the following to get the tomcat user (who is running the jenkins instance) his own set of keys:
sudo mkdir /home/tomcat
sudo chown tomcat:tomcat /home/tomcat
sudo -u tomcat mkdir .ssh
sudo -u tomcat ssh-keygen -t rsa -C "PLEASE_SET_YOUR_EMAIL_ADDRESS"
After doing this, I've confirmed that the tomcat user can access github over SSH:
sudo -u tomcat ssh -T email@example.com
Hi workcloud-jenkins! You've successfully authenticated, but GitHub does not provide shell access.
I've copied the id_rsa.pub keys to a deploy user account that has access to the private repo.
But when setting up the CI job that needs to access the private repo, the following error gets displayed.
Failed to connect to repository : Command "/opt/bitnami/git/bin/git ls-remote -h firstname.lastname@example.org:workcloud/workcloud.git HEAD" returned status code 128:
stderr: ssh: /opt/bitnami/common/lib/libcrypto.so.1.0.0: no version information available (required by ssh)
Host key verification failed.
fatal: The remote end hung up unexpectedly
I've been banging my head against the wall for hours, but nothing on Google has helped.
What's the problem here - I'm so close!