[
https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163458#comment-163458
]
SCM/JIRA link daemon commented on JENKINS-13007:
------------------------------------------------
Code changed in jenkins
User: Nicolas De loof
Path:
src/main/java/hudson/plugins/git/GitAPI.java
http://jenkins-ci.org/commit/git-plugin/db53ccea4188e182336f5e5c579f6adce34f6ecb
Log:
Merge pull request #71 from vjuranek/JENKINS-13007
[FIXED JENKINS-13007] Handle special meaning of some charactes on Window...
Compare: https://github.com/jenkinsci/git-plugin/compare/cef9941...db53cce
> 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
