[
https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160721#comment-160721
]
Vincent Latombe commented on JENKINS-13007:
-------------------------------------------
I've looked into this issue, and I've found the following workaround :
on windows, you have to use GIT_HOME\bin\git.exe instead of GIT_HOME\cmd\git.cmd
The problem is that
https://github.com/jenkinsci/git-plugin/commit/e4cbe704fc1740d1fc6e3e0887476b95db230c60
added ^{commit} option to git rev-parse to dereference tags. However when
using the batch wrapper, it fails because ^ is an escape character in windows
batches.
> Git plugin cannot find revision to build on Windows
> ---------------------------------------------------
>
> Key: JENKINS-13007
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13007
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Environment: Windows 2008 Server 64 Bit
> NTFS
> Reporter: ritzmann
> Assignee: Nicolas De Loof
> Priority: Critical
>
> After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on
> Windows build slaves started failing like this:
> Started by user anonymous
> Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app
> Checkout:my-app / d:\hudson\workspace\my-app -
> hudson.remoting.Channel@95ff886:win-slave1
> Using strategy: Default
> Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f33337534b34
> (origin/master)
> Checkout:my-app / d:\hudson\workspace\my-app -
> hudson.remoting.LocalChannel@470a4b80
> Fetching changes from 1 remote Git repository
> Fetching upstream changes from d:\hudson\shared\repo.git
> ERROR: Couldn't find any revision to build. Verify the repository and branch
> configuration for this job.
> The builds on our Linux slaves are not affected. Wiping the workspaces on the
> Windows slaves did not help. Both clones and checkouts/updates seem to fail
> with the same error. Downgrading back to 1.1.14 made the Windows builds work
> again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
