git submodule update --init 给出错误致命：需要单个修订版无法在子模块路径中找到当前修订版

Question

When i execute git submodule update --init I get error

fatal: Needed a single revision Unable to find current revision in submodule path 'plugins/pluginname'.

Actually I was trying to run a Jenkins Job to deploy it. I added Recursively update submodules as additional behavior in Jenkins. FATAL: Command "git.exe submodule update --init --recursive" returned status code -1: This is occurring only from my local as same command is working for others.

Answer 1

尝试git submodule foreach git pull

Answer 2

It's an example of a hidden actual error in Git, a UX pitfall typical to Git.

In my case the real error was that I was using a submodule pinned to a branch that doesn't exist anymore (eg feature branch that was already merged and deleted via Gitlab). Verify if that's the case for you as well and if it is, point the submodule to a new branch.

Answer 3

I tried many other suggestions that didn't work, but the commands that worked for me are:

git submodule sync
git submodule update --init

Answer 4

For people falling into this problem with Jenkins I actually found the solution here . You can select

Wipe out repository & force clone

This works but leads to longer checkout

Answer 5

For TeamCity users.

Open your VCS Root Settings and change submodules mode from checkout to ignore. Then you can finally checkout submodules manually in your scripts without this error.

Answer 6

An older question, but here's what worked for me.

The error happens because the fetch command the git submodule update runs isn't finding the branch. In my case, I could sync and update all I wanted but it still didn't fix it. I eventually found my solution in a related answer , but I'm adding here for anyone else runs into it.

If the parent repo was shallowly cloned, then remote.origin.fetch in the submodule is restricted to the branch set in the .gitmodule (or the default branch). In my case, I was only running into the problem with Gitlab CI when I was trying to run tests from the parent repo on a branch of the submodule. Submodules worked fine if .gitmodules is modified as part of a commit, but not if changing branch on the runner itself.

If you're running into this error you can check/fix your submodules with:

git submodule foreach git config --get remote.origin.fetch
# Entering 'good_submodule'
# +refs/heads/*:refs/remotes/origin/*
# Entering 'bad_submodule'
# +refs/heads/someBranch:refs/remotes/origin/someBranch

And you can similarly correct it:

# selectively fix
git -C bad_submodule config remote.origin.fetch '+refs/heads/*:refs/remotes/origin/*'
# ensure all submodules can access everything
git submodule foreach git config remote.origin.fetch '+refs/heads/*:refs/remotes/origin/*'