检查Checkout子模块或新功能时Team Services上的错误？ [英] Bug on Team Services when Checkout Submodules is checked, or new functionality?

问题描述

您好，

我正在尝试使用嵌套子模块构建解决方案项目。有一个主git存储库，这个主存储库有一个git子模块（submodule1），这个子模块1有自己的git子模块（子模块1.1）。

I am trying to build a solution project with nested submodules. There is a main git repository, this main repository has a git submodule (submodule1), and this submodule1 has its own git submodule (submodule1.1).

在Build Repository选项中有一个"标签abp =" 879" for =" checkout-submodules"> Checkout子模块< / label>"我检查过的选项。如果只有一个级别的git子模块，建立一个解决方案是有效的，
但是如果你有两个或更多的子模块级别它就不起作用。看一下跟踪，我看到了一个"git submodule init"。命令，但我认为它还应该添加一个"递归"的命令。选项，例如" git submodule update --init
- recursive "为了下载所有git子模块。或者至少，在构建属性页面中，可能是一个新选项，例如"< label abp =" 879"。 for =" checkout-submodules">递归检出子模块"。< / label>

On Build Repository options there is a "<label abp="879" for="checkout-submodules">Checkout submodules</label>" option that I have checked. Building a solution works propertly if there is only one level of git submodules, but it doesn´t work if you have two or more submodule levels. Taking a look at traces, I see a "git submodule init" command, but I think it should add also a "recursive" option, something like "git submodule update --init --recursive" in order to download all git submodules. Or at least, in the build properties page, perhaps could be a new option something like "<label abp="879" for="checkout-submodules">Checkout submodules recursively".</label>

推荐答案

问候，

很抱歉给您带来不便。请创建支持票，团队成员将帮助您。

Sorry for inconvenience caused. please create support ticket, someone from the team will help you.

https://www.visualstudio.com/en-us/support/support-overview-vs.aspx

https://www.visualstudio.com/en-us/support/support-overview-vs.aspx

问候，

这篇关于检查Checkout子模块或新功能时Team Services上的错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！