Minor http.sslverify=false is ignored!
>>>
hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: https://****: cannot open git-upload-pack
at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:344)
Caused by: org.eclipse.jgit.api.errors.TransportException: https://***: cannot open git-upload-pack
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137)
Caused by: org.eclipse.jgit.errors.TransportException: https://***: cannot open git-upload-pack
at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:499)
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:196)
- is related to
-
JENKINS-23050 Slave unable to clone from Git over HTTPS due to self signed certificate
-
- Closed
-
[JENKINS-19726] JGIT Error in combination with self signed certificate and https repo
Manuel
created issue -
Refer to "Why Not JGit" at https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-WhyNotJGit for more details
changed from "blocker" to "minor", as this only affects (experimental) jgit implementation, that is known to have some limitations
| Priority | Original: Blocker [ 1 ] | New: Minor [ 4 ] |
Manuel
added a comment - but...
I have this issue in this plugin too:
https://github.com/jenkinsci/literate-plugin
Manuel
added a comment - but...
I have this issue in this plugin too:
https://github.com/jenkinsci/literate-plugin http.sslverify is a git-cli option, so to support this use case, have to find the equivalent for JGit and provide this as a (global ?) configuration option
| Issue Type | Original: Bug [ 1 ] | New: Task [ 3 ] |
| Issue Type | Original: Task [ 3 ] | New: Improvement [ 4 ] |
| Component/s | New: git-client [ 17423 ] | |
| Component/s | Original: git [ 15543 ] |
The jgit implementation embedded in Git plugin 1.5.0 and in Git client plugin 1.2.0 were not sufficient for my use cases, nor for the use cases of many other Jenkins users. The limitations in the upstream jgit implementation were too much for what we needed. I think that's why the default git provider was switched back to command line git, instead of jgit.
You might try switching to use the command line git instead of JGit. There is a system level configuration (in http://yourserver/configure which will define a git installation to use, then you can select whether to use jgit or the command line git for a specific job.