Jon Topper created JENKINS-13634:
------------------------------------
Summary: Multiple SCM plugin fails when used with matrix project
and git plugin
Key: JENKINS-13634
URL: https://issues.jenkins-ci.org/browse/JENKINS-13634
Project: Jenkins
Issue Type: Bug
Components: git, multiple-scms
Affects Versions: current
Environment: Ubuntu Lucid, latest packaged release
Reporter: Jon Topper
Assignee: Nicolas De Loof
I've created a matrix project, though currently with only one target for the
variable 'box_type'.
To this project, I've added two Git repositories using the Multiple SCMs
plugin. I've given each repository a "Local subdirectory for repo" so that
they will check out side-by-side in the workspace.
On running the build, the initial checkout of both repos into the standard
workspace location succeeds.
When running the configuration matrix, I get the following error:
{code}
Checkout:centos6-vagrant-box /
/var/lib/jenkins/jobs/test_puppet/workspace/box_type/centos6-vagrant-box -
hudson.remoting.LocalChannel@42dd67cf
Using strategy: Default
Last Built Revision: Revision 6be03c6886d1db90bfc94a10d4d6098fe5b84b77
(origin/HEAD, origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from
[email protected]:scalefactory/puppet-with-cukes.git
Commencing build of Revision 6be03c6886d1db90bfc94a10d4d6098fe5b84b77
(origin/HEAD, origin/master)
Checking out Revision 6be03c6886d1db90bfc94a10d4d6098fe5b84b77 (origin/HEAD,
origin/master)
FATAL: Could not checkout null with start point
6be03c6886d1db90bfc94a10d4d6098fe5b84b77
hudson.plugins.git.GitException: Could not checkout null with start point
6be03c6886d1db90bfc94a10d4d6098fe5b84b77
at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:872)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1280)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1264)
at hudson.FilePath.act(FilePath.java:832)
at hudson.FilePath.act(FilePath.java:814)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1264)
at
org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1434)
at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: hudson.plugins.git.GitException: Command "/tmp/git-with-logging
checkout -f 6be03c6886d1db90bfc94a10d4d6098fe5b84b77" returned status code 128:
stdout:
stderr: fatal: reference is not a tree: 6be03c6886d1db90bfc94a10d4d6098fe5b84b77
at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:779)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:741)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:751)
at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:859)
... 13 more
{code}
There are two repositories at play here: "cumberbatch" and "puppet-with-cukes".
The revision SHA of 6be03c6886d1db90bfc94a10d4d6098fe5b84b77 is the latest
revision of "cumberbatch", however the failing "git checkout" command is
attempting to use that SHA with the "puppet-with-cukes" repository, and I
believe this is the reason for the failure condition.
--
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