[ 
https://issues.jenkins-ci.org/browse/JENKINS-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160079#comment-160079
 ] 

Eric Anderson commented on JENKINS-8149:
----------------------------------------

This just bit me too :(
                
> Git submodule fetch uses (incorrect) parent refspec
> ---------------------------------------------------
>
>                 Key: JENKINS-8149
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-8149
>             Project: Jenkins
>          Issue Type: Bug
>          Components: git
>    Affects Versions: current
>         Environment: hudson 1.385, Hudson git plugin 1.1.3
>            Reporter: Cody Cutrer
>            Assignee: abayer
>
> When using the "recursively update submodules" option, as well as a specific 
> refspec, it tries to apply the same refspec when fetching changes for the 
> submodule, causing spurious errors in the log:
> {quote}
> Checkout:test / /home/punkyb/hudson/amd64-lucid/workspace/test - 
> hudson.remoting.Channel@61ae0436:slave-amd64-lucid
> Using strategy: Default
> Last Built Revision: Revision becbe8166b41940e842548f8dcc895ddafc67ceb 
> (origin/release/1.2)
> Checkout:test / /home/punkyb/hudson/amd64-lucid/workspace/test - 
> hudson.remoting.LocalChannel@23226fe1
> GitAPI created
> Fetching changes from the remote Git repository
> Fetching upstream changes from ssh://sourcecontrol/parent.git
> [test] $ git fetch -t ssh://sourcecontrol/parent.git/parent.git 
> refs/heads/featurebranch
> [test] $ git ls-tree HEAD
> Trying to fetch submodule into 
> /home/punkyb/hudson/amd64-lucid/workspace/test/submodule
> GitAPI created
> Fetching upstream changes from ssh://sourcecontrol/submodule.git
> [submodule] $ git fetch -t ssh://sourcecontrol/submodule.git 
> refs/heads/featurebranch
> Problem fetching from submodule submodule - could be unavailable. Continuing 
> anyway
> {quote}

--
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

        

Reply via email to