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

GIT with Jenkins failed with error "self signed certificate in certificate chain"

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I am trying to configure GIT with Jenkins( source Code Management section). As soon I enter repository URL , Error pops up and stating:
      Failed to connect to repository : Command "C:\Program Files\Git\bin\git.exe ls-remote -h https://xxx.xxxxx.xxxxx.xxxxxx.xxx/stash/scm/project/project.git] HEAD"
      returned status code 128: stdout: stderr: fatal:
      unable to access 'https://xxx.xxxxx.xxxxx.xxxxxx.xxx/stash/scm/project/project.git/':
      SSL certificate problem: self signed certificate in certificate chain

      Please guide/help how I can I skip this security Check with Jenkins (git plugin) or How self signed certificate can be installed in system to work with Jenkins on windows 7.|

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment - - edited

          Please request help from the places which more people read rather than using a bug report to request help.

          There are far fewer people who read git client plugin bug reports than read

          On this specific issue, I'm opposed to self-signed certificates, especially over commercial products like Atlassian Stash.  Your company has purchased Atlassian Stash.  You'll be much better served by also purchasing and installing an SSL certificate for the server, rather than fighting with self-signed certificates. 

          Yes, it is possible in some cases to make self-signed certificates work, but they are brittle and hard to maintain.  You'll spend more maintaining self-signed certificates than the cost of the SSL certificate.

          Show
          markewaite Mark Waite added a comment - - edited Please request help from the places which more people read rather than using a bug report to request help. There are far fewer people who read git client plugin bug reports than read chat on the Jenkins internet relay channel , the jenkins channel on gitter , and mailing lists like Jenkins users . On this specific issue, I'm opposed to self-signed certificates, especially over commercial products like Atlassian Stash.  Your company has purchased Atlassian Stash.  You'll be much better served by also purchasing and installing an SSL certificate for the server, rather than fighting with self-signed certificates.  Yes, it is possible in some cases to make self-signed certificates work, but they are brittle and hard to maintain.  You'll spend more maintaining self-signed certificates than the cost of the SSL certificate.

            People

            • Assignee:
              markewaite Mark Waite
              Reporter:
              vikaskumarchoudhary Vikas Kumar
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: