Yes I agree this, this has happened just recently. I think our back traces are slightly different, I have an IOException you have a NullPointerException. With a NullPointerException I think you might just have to fill out something in the web page that you didn't have to in the past. I'm thinking mine has to do something with the file system or the OS but the my exception doesn't say what the IO error was about.

Additionally,

I do the following as tomcat in the workspace.

-bash-4.1$ git clone https://github.com/EMSL-MSC/go-rpms.git go-master
Initialized empty Git repository in /srv/jenkins/workspace/go-master/.git/
remote: Counting objects: 45, done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 45 (delta 20), reused 25 (delta 3)
Unpacking objects: 100% (45/45), done.
-bash-4.1$ cd go-master/
-bash-4.1$ ls
cgo.patch COPYING download.bat download.sh go-goos.c-no-envvars.diff go.spec install.bat Makefile README.md runit.bat uninstall.bat
-bash-4.1$ logout

and it works.

Ah, additionally I was at git client 1.5.0 and just recently got 2.0 and now I'm getting something similar to Ricardo.

Building on master in workspace /srv/jenkins/workspace/go-master
Cloning the remote Git repository
Cloning repository https://github.com/EMSL-MSC/go-rpms.git
git --version
git version 1.7.1
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not clone https://github.com/EMSL-MSC/go-rpms.git
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:286)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:828)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557)
at hudson.model.Run.execute(Run.java:1665)
at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)
at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43)
Caused by: hudson.plugins.git.GitException: Failed to connect to https://github.com/EMSL-MSC/go-rpms.git
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getURLWithCrendentials(CliGitAPIImpl.java:1380)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getURLWithCrendentials(CliGitAPIImpl.java:1326)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:47)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280)
... 11 more
ERROR: null
Finished: FAILURE

I've downgraded the GIT Client to 1.4.0 and can again clone repositories, but only if the to the GitHub repository ends in .git.

It used to work without the .git as I had several projects configured like this. But maybe the GitHub plugin allowed this, and it's currently disabled because of https://issues.jenkins-ci.org/browse/JENKINS-20201.

Code changed in jenkins
User: Nicolas De Loof
Path:
src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
http://jenkins-ci.org/commit/git-client-plugin/ddfde14d27aa6cd802dfc9897506eae4095b4f37
Log:
JENKINS-20189 automatically append .git to repo URL
just as git-cli does when base URL don't resolve to a git repo

Thanks for the update on the .git aside. But it was an aside, the original issue that 'git clone' doesn't work with git client versions above 1.4.0 (in my case) is still true.

(The title is a bit misleading but the problem exists.)

This was marked "Resolved" some time ago. Now marking it "Closed" since there is

markewaite Preceding comment is incomplete.

Jira for that comment does not allow me to edit the comment. The comment should have said that I am marking it Closed since git versions prior to 1.7.10 do not support credentials, and credentials are now a key part of the git plugin use model.

markewaite:

Jira for that comment does not allow me to edit the comment

Probably thanks to 'Closed' status, just like it doesn't allow editing the issue. Hoping for INFRA-119.