How to debug Jenkins error message “could not find a suitable ssh-agent provider”?

后端 未结 3 1323
轻奢々
轻奢々 2021-01-05 03:50

I\'m using Jenkins on Win7 and i\'ve installed tomcat for ssh-agent plugin. And I could clone my GitLab project via git bash via ssh.
But if I build the pro

相关标签:
3条回答
  • 2021-01-05 04:12

    Assuming you've installed Windows Git on Windows slave, it comes with ssh-agent binary (e.g. C:\Program Files\Git\usr\bin). Try adding its path to system variable PATH.


    Otherwise untick SSH Agent and choose the credentials by selecting Credentials from dropdown in Source Code Management section.


    Another way is to generate personal API token (OAuth) for that GitHub user and include that along with your repository address, e.g.

    git clone https://4UTHT0KEN@github.com/foo/bar
    
    0 讨论(0)
  • 2021-01-05 04:14

    For windows, the plugin still requires Tomcat to be installed in both master and slave.

    0 讨论(0)
  • 2021-01-05 04:16

    Check the version of your ssh-agent used by Jenkins.
    This bug (for linux, but could apply to Windows too) reports (10 days ago, January 2014) this very same error message:
    "JENKINS-20276: Native Library Error after upgrading ssh-agent from 1.3 to 1.4".

    Downgrading to 1.3 resolves the issue.


    Update 2019, five years later: as commented, this should be fixed now.

    ssh-agent.exe is part of a Git for Windows distribution

    D:\git\git>where ssh-agent.exe
    D:\prgs\gits\current\usr\bin\ssh-agent.exe
    

    (provided path/to/git/usr/bin is first in the %PATH% used by Jenkins)

    0 讨论(0)
提交回复
热议问题