[
https://issues.jenkins-ci.org/browse/JENKINS-14026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163697#comment-163697
]
tsondergaard commented on JENKINS-14026:
----------------------------------------
I'm on jenkins 1.467 and with git plugin version 1.1.19 I get the following
error. After downgrading to version 1.1.16 the problem went away. Is it the
same problem as reported in this bug?
Here's the log output with git plugin 1.1.19 and a fresh workspace:
Started by upstream project "easyviz-5-integrate" build number 21
[EnvInject] - Loading node environment variables.
Building remotely on bob-w7-64 in workspace
c:\jenkins\workspace\easyviz-5-integrate\arch\win32
Checkout:win32 / c:\jenkins\workspace\easyviz-5-integrate\arch\win32 -
hudson.remoting.Channel@2f860a43:bob-w7-64
Using strategy: Default
Last Built Revision: Revision d7e55522feb251a876a5e8c1d1370686b77db1b5
(origin/for-5.0.0/bug-14364-build-manual)
Fetching changes from 1 remote Git repository
Fetching upstream changes from
ssh://buildu...@git.medical-insight.com/var/git/easyviz.git
Pruning obsolete local branches
Commencing build of Revision e3e816d8d00386d76bfb615044c0acf1fa89f963
(origin/for-5.0.0/bug-14466-cppcheck)
Merging Revision e3e816d8d00386d76bfb615044c0acf1fa89f963
(origin/for-5.0.0/bug-14466-cppcheck) onto release/5.0.0
FATAL: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse
origin/release/5.0.0^^\{commit\}" returned status code 128:
stdout: origin/release/5.0.0^^\{commit\}
stderr: fatal: ambiguous argument 'origin/release/5.0.0^^\{commit\}': unknown
revision or path not in the working tree.
Use '--' to separate paths from revisions
hudson.plugins.git.GitException: Command "C:\Program Files
(x86)\Git\bin\git.exe rev-parse origin/release/5.0.0^^\{commit\}" returned
status code 128:
stdout: origin/release/5.0.0^^\{commit\}
stderr: fatal: ambiguous argument 'origin/release/5.0.0^^\{commit\}': unknown
revision or path not in the working tree.
Use '--' to separate paths from revisions
at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:786)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:748)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:758)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:261)
at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1214)
at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1197)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
> git plugin doesn't support branch name contains slash ("/")
> -----------------------------------------------------------
>
> Key: JENKINS-14026
> URL: https://issues.jenkins-ci.org/browse/JENKINS-14026
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Reporter: Yi Wen
> Labels: branch
>
> When a branch contains slash (/), if we try to specify such a branch in
> "Branch Name" field, it will not be able to fetch such branches. If we leave
> branch name as **, the job can fetch branch name containing slash without
> problem.
> I am not a Java person, but this method looks suspicious in Branch.java, just
> trying to help debug
> private static String strip(String name) {
> return name.substring(name.indexOf('/', 5) + 1);
> }
>
--
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
