Thanks for the report. My apologies that I didn't think to test a workspace containing a space with an authenticating git checkout. I'll include that in future tests before release.

You'll probably need to fall back to an earlier version of the git client plugin (rather than the git plugin) to avoid that issue. I suspect that is a regression introduced in the git client plugin 2.4.4 update when it switched from placing temporary files in the system temporary directory to placing them in a temporary directory near the workspace. I think that the git client plugin 2.4.2 should be enough to allow you to run.

Some double quotes will need to be carefully inserted into certain locations in the scripts if the path to the temporary file contains spaces. Unfortunately, that requires a different set of command processor escaping rules, and will create more complicated logic in a section of code that already feels too complicated.

I won't be able to do deep investigation on the issue until next week at the earliest.

Code changed in jenkins
User: Mark Waite
Path:
src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
src/test/java/org/jenkinsci/plugins/gitclient/CredentialsTest.java
http://jenkins-ci.org/commit/git-client-plugin/ab1ad21e4bbab4f03fca23f3f331493769370c20
Log:
JENKINS-43931 support private keys w/passphrase in Windows dirs with spaces

The temporary file protection code (correctly) prefers to place
sensitive temporary files near the workspace rather than placing them
in the system temporary directory. The Windows git implementation
(through at least git 2.12.2) fails to authenticate if the value of
GIT_SSH is a path which includes a space.

If the workspace temporary directory name contains a space, the system
temporary directory will be used instead. There is already code in
the CliGitAPIImpl class which writes a warning if the system temporary
directory includes a space in its path.

Fixed in git client plugin 2.4.5, released 29 Apr 2017

Hi markewaite, I'm still receiving a similar error message using git client plugin version 2.4.5 and my project name don't have space in it. 

Building in workspace C:\Program Files (x86)\Jenkins\jobs\eTCMGeraNovaVersao\workspace
Cloning the remote Git repository
Cloning repository http://Git/asi/eTCM.git
git.exe init C:\Program Files (x86)\Jenkins\jobs\eTCMGeraNovaVersao\workspace # timeout=10
Fetching upstream changes from http://Git/asi/eTCM.git
git.exe --version # timeout=10
using GIT_ASKPASS to set credentials Usuário para acessar o Gitlab no servidor Git
git.exe fetch --tags --progress http://Git/asi/eTCM.git +refs/heads/:refs/remotes/origin/
ERROR: Timeout after 10 minutes
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "git.exe fetch --tags --progress http://Git/asi/eTCM.git +refs/heads/:refs/remotes/origin/" returned status code -1:
stdout:
stderr: 'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1877)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1596)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:71)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:348)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:545)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1067)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1107)
at hudson.scm.SCM.checkout(SCM.java:496)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1281)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:405)
ERROR: null

paulofgp the path to your workspace includes a space, since the git init command is:

git.exe init C:\Program Files (x86)\Jenkins\jobs\eTCMGeraNovaVersao\workspace

Since you're using http protocol, I assume you are authenticating with a username and password (rather than with a passphrase protected private key as described in this bug report). Can you confirm that you're using a username / password combination?

The username / password path was not modified in the git client plugin 2.4.5 release because I did not see the problem on that path. The only path where I saw the problem was in the private key with passphrase path. However, now that I read the bug report again, the original submitter was using a username / password with http. I'll need to do further testing with the username / password path to see if I can duplicate the problem.

I've created a snapshot build which contains the one line modification to handle username / password cases. Could you test drive it to see if it resolves your issue?

I'm really using username and password.

I tested your snapshot build and it worked.

Tks for your help.

Code changed in jenkins
User: Mark Waite
Path:
src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
http://jenkins-ci.org/commit/git-client-plugin/4f27a7010ea9d2aa8516edd44791561f99792d41
Log:
JENKINS-43931 Allow username/password workspaces with space in path

Prior fix only handled ssh passphrase protected private keys

Note that the issue is only visible on Windows and only with workspaces
whose full path includes a space.

Hi Mark, I just updated with your SNAPSHOT and it worked.  Thank you.

Code changed in jenkins
User: Mark Waite
Path:
src/test/java/org/jenkinsci/plugins/gitclient/CredentialsTest.java
http://jenkins-ci.org/commit/git-client-plugin/5c74414a6ef50488e9006d83f127a69b6a7b8da0
Log:
Test special characters in credentials workspace path

JENKINS-44041 - Windows authenticated git checkout fails if '(' or ')' in path to workspace
JENKINS-43931 - Windows authenticated git checkout fails if ' ' in path to workspace
JENKINS-44127 - Authenticated git checkout fails if '%' in path to workspace (Windows & Linux)

Code changed in jenkins
User: Mark Waite
Path:
src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
http://jenkins-ci.org/commit/git-client-plugin/8a2ddf222f4463e2458e387121bf8d4c7840c37a
Log:
Fix special characters bugs in credentials workspace path

JENKINS-44041 - Windows authenticated git checkout fails if '(' or ')' in path to workspace
JENKINS-43931 - Windows authenticated git checkout fails if ' ' in path to workspace
JENKINS-44127 - Authenticated git checkout fails if '%' in path to workspace (Windows & Linux)

Also safeguards against use for "`" (grave) in a workspace path.
Jenkins already guards against that, but the added safety check is low
cost and passes the credentials tests.