Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-65894

ssh credential not usable for http access to git repository

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hi,

      While trying to integrate Jenkins with GIT we are observing below error. please help to resolve

      Failed to connect to repository : Command "git.exe ls-remote -h – http://172.17.80.86:3000/TTSL/TTL_Postpaid_BPM.git HEAD" returned status code 128:
      stdout:
      stderr: ssh: connect to host 172.17.80.86 port 22: Connection timed out
      fatal: Could not read from remote repository.

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          Please don't use the issue tracker for questions. When you use the issue tracker for questions, you limit the number of people who will see your question and thus you limit the number of people who will reply to your question.

          Use the Jenkins user mailing list or the Jenkins chat channels for questions. Instead of 1-3 people seeing your questions, 10-100 people will see your question and may be willing to assist.

          In your example, you're using the HTTP protocol to attempt to open the remote repository, but it appears from the error message that you're using a private key credential. HTTP and HTTPS access to a remote repository require a username/password credential, not a private key credential. Private key credentials require SSH access to the remote repository.

          Show
          markewaite Mark Waite added a comment - Please don't use the issue tracker for questions. When you use the issue tracker for questions, you limit the number of people who will see your question and thus you limit the number of people who will reply to your question. Use the Jenkins user mailing list or the Jenkins chat channels for questions. Instead of 1-3 people seeing your questions, 10-100 people will see your question and may be willing to assist. In your example, you're using the HTTP protocol to attempt to open the remote repository, but it appears from the error message that you're using a private key credential. HTTP and HTTPS access to a remote repository require a username/password credential, not a private key credential. Private key credentials require SSH access to the remote repository.

            People

            Assignee:
            markewaite Mark Waite
            Reporter:
            saitama_genos Naveen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: