turns out that i was using a same key pair for 2 different github accounts.
On Monday, July 6, 2015 at 2:11:46 PM UTC-7, niristotle okram wrote: > > Versions: > > - Ruby : ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux] > - Capistrano : 'capistrano', '2.15.5' > > Platform: > > - Working on.... RHEL 6.6 > - Deploying to... RHEL 6.6 > > Logs: > > - http://pastebin.com/dbrTb2hs > > Files: > > - Capfile : > - deploy.rb http://pastebin.com/DqYtXPfg > - dev.rb http://pastebin.com/Hsn33pXQ > > > Hey guys, can you let me know why the cap2 is failing, when it tries to > connect to the github? I can verify that it works i execute the commands > manaully on the jenkins slaves (they does the deploy). I refer the > http://capistranorb.com/documentation/getting-started/authentication-and-authorisation/ > > it appears that the capistrano is running the command as only: git > ls-remote [email protected]:Hewlett-PackardDevOps/ows-oss-test.git dev.. > Rather than > deploy_user@serverX 'git ls-remote > [email protected]:Hewlett-PackardDevOps/ows-oss-test.git dev' > > > So executing this on the jenkins slave: > > [jenkins@ip-10-0-0-90 ~]$ git ls-remote ssh://[email protected]:some_name.git > dev > ssh: Could not resolve hostname github.com:some_name: Name or service not > known > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > > > The above response/ERROR is what i have when executing the 'cap dev > deploy' > > -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/6cf48792-7b21-43ec-8971-34f7e089761f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
