Yes, you're understanding the message correctly. That is an instance of JENKINS-30600.
On Thu, Jul 2, 2020 at 2:51 AM Martin Schmude <[email protected]> wrote: > Hi all, > I need help with an issue related to the git step in a pipeline job, that > is executed in a Docker container. > The pipeline looks like this: > > node('Docker-capable-node') { > docker.inside('image-with-git-installed').inside { > git credentialsId: 'my-credentials', url: ' > https://gitlab.mycompany.com/myproject' > } > } > > This fails with > > > using credential my-credentials > Warning: JENKINS-30600: special launcher > org.jenkinsci.plugins.docker.workflow.WithContainerStep$Decorator$1@12e7bf52; > decorates RemoteLauncher[hudson.remoting.Channel@*XXX*] will be ignored (a > typical symptom is the Git executable not being run inside a designated > container) > Cloning the remote Git repository > ERROR: Error cloning remote repo 'origin' > hudson.plugins.git.GitException: Command "git fetch --tags --progress > https://gitlab.mycompany.com/myproject.git > <https://gitlab.consulting.sltc.com/appmod/qm/innowake-documentation/documentation.git> > +refs/heads/*:refs/remotes/origin/*" returned status code 128: > stdout: > stderr: fatal: unable to access > 'https://gitlab.mycompany.com/myproject/documentation.git/ > <https://gitlab.consulting.sltc.com/appmod/qm/innowake-documentation/documentation.git/>': > Peer's Certificate issuer is not recognized. > > > Am I right that this is the already known issue > https://issues.jenkins.io/browse/JENKINS-30600? > > I am pretty sure that this is not a matter of SSL certificates, because > this works without SSL certificate issues: > node('Docker-capable-node') { > docker.inside('image-with-git-and-ssl-certificate-installed').inside { > sh 'git clone https://gitlab.mycompany.com/myproject' > } > } > *(I had to install a SSL certificate in that Docker image > "image-with-git-and-ssl-certificate-installed" to avoid certificate > issues.)* > > Of course I'd prefer the builtin git step. Am I right that I can't due to > the JENKINS-30600 issue? > What workaround do you recommend? The > sh 'git clone ...' > is an obvious way to go, but maybe there is something better? > > Thanks in advance. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" 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/jenkinsci-users/d53e698d-946b-4a33-8560-54f42edf4ca2o%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/d53e698d-946b-4a33-8560-54f42edf4ca2o%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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/jenkinsci-users/CAO49JtEiyHTp_fFvvnTXVVwrb9%3D_efdevRHVw63_1G73vpvASw%40mail.gmail.com.
