You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a submodule that is set to use a branch that is not merged into the default (master) branch. The branch I am using is called "dev".
When a deployment is triggered in Kudu, it fails with the following command, with the following error message:
git.exe submodule update --init --recursive
fatal: reference is not a tree: 0a1fd6dc0ac024378610ec25ec74dcd8400bb478
Unable to checkout '0a1fd6dc0ac024378610ec25ec74dcd8400bb478' in submodule path ...
If I run the following commands from the debug console (some of the same commands Kudu uses on the main repo...), the submodule update works fine after that
cd [submoduledir]
git.exe remote add -t dev external [remoteurl]
git.exe fetch external --progress
The -t dev arguments are probably not needed, they just happened to be the ones I used.
if the remote add command fails with "remote external already exists.", remove the remote and re-add it (better than doing nothing because the remote url could have changed in the submodule).
I imagine it would require parsing the .gitmodules file to locate the submodule directories and branches. I would submit a patch myself but was hoping someone with more familiarity with the project's build and testing process, could fix this more efficiently if I provided enough information.
(Edited out last command that was not necessary)
The text was updated successfully, but these errors were encountered:
I have a submodule that is set to use a branch that is not merged into the default (master) branch. The branch I am using is called "dev".
When a deployment is triggered in Kudu, it fails with the following command, with the following error message:
git.exe submodule update --init --recursive
If I run the following commands from the debug console (some of the same commands Kudu uses on the main repo...), the submodule update works fine after that
The -t dev arguments are probably not needed, they just happened to be the ones I used.
if the remote add command fails with "remote external already exists.", remove the remote and re-add it (better than doing nothing because the remote url could have changed in the submodule).
Here's the file that could be a starting point for what to change: https://github.com/projectkudu/kudu/blob/master/Kudu.Core/SourceControl/Git/GitExeRepository.cs
I imagine it would require parsing the .gitmodules file to locate the submodule directories and branches. I would submit a patch myself but was hoping someone with more familiarity with the project's build and testing process, could fix this more efficiently if I provided enough information.
(Edited out last command that was not necessary)
The text was updated successfully, but these errors were encountered: