巡航控制源安全块

发布于 2024-07-09 01:26:10 字数 812 浏览 6 评论 0原文

正在运行的构建机器有很多项目,但我们只遇到一个问题。

两个项目非常相似,一个在调试模式下构建,另一个在发布模式下构建。 他们都清除了项目目录,然后从源代码安全地进行了完整的获取。 调试版本可以很好且快速地获取源代码,但是发布版本需要很长时间才能获取源代码(它在 CheckingModifications 部分暂停很长时间,而调试版本则不会暂停很长时间)。 源控制块是相同的(包含在单个文件中),如下所示:

<sourcecontrol type="vss" autoGetSource="true" applyLabel="false">
    <executable>C:\Program Files\Microsoft Visual Studio\VSS\win32\SS.EXE</executable>
    <project>$/Projects</project>
    <username>####</username>
    <password>####</password>
    <ssdir>\\####\SourceCode\VSS</ssdir>
    <workingDirectory>D:\Projects\</workingDirectory>
    <culture>en-GB</culture>
    <cleanCopy>True</cleanCopy>
</sourcecontrol>

任何人都知道为什么版本构建源控制块速度较慢?

The build machine at work has many projects, but we are only experiencing a problem with one.

Two projects are very similar, one builds in debug mode, the other in release mode. They both clear out the projects directory, and then does a full Get from source safe. The debug build gets the source fine and fairly quickly, but the release build takes ages to get the source (It pauses for a long time on the CheckingModifications part, whereas the debug build does not pause for nearly as long). The sourcecontrol blocks are identical (included from a single file), and are as follows:

<sourcecontrol type="vss" autoGetSource="true" applyLabel="false">
    <executable>C:\Program Files\Microsoft Visual Studio\VSS\win32\SS.EXE</executable>
    <project>$/Projects</project>
    <username>####</username>
    <password>####</password>
    <ssdir>\\####\SourceCode\VSS</ssdir>
    <workingDirectory>D:\Projects\</workingDirectory>
    <culture>en-GB</culture>
    <cleanCopy>True</cleanCopy>
</sourcecontrol>

Any one have any ideas on why the release builds source control block is slower?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

你怎么这么可爱啊 2024-07-16 01:26:10

最后我们从 SourceSafe 切换到 SourceGear Vault(主要是为了分支功能,但速度和可靠性也是重要因素)。

我们还将构建机器从旧 PC 移至与源服务器的连接速度为 1Gb/s(而不是 100Mb/s)的服务器,这有很大帮助。

最后,当我在与旧构建机器相同的机器(好吧,克隆)上安装和测试 Vault 时,它将源获取操作从大约 10 分钟减少到 5 分钟。一旦将其安装在构建服务器上,源获取现在时间约为 1 分钟。

我对任何人的建议是从 SourceSafe 切换到其他任何东西......你不会后悔的。

In the end we have switched from SourceSafe to SourceGear Vault (mainly for branching features, but speed and reliability were also large factors).

We have also moved our build machine from an old pc to a server which has a 1Gb/s connection to the source server, rather than 100Mb/s, which has helped considerably.

In the end when I was installing and testing Vault on the same machine (well, a clone) as the old build machine, it was cutting the source get operation from around 10 mins to 5. Once it was installed on the build server source get time is now around 1min.

My advice to anyone is just to switch from SourceSafe to anything else...you wont regret it.

2024-07-16 01:26:10

调试和发布版本是否同时运行? 如果是这样,我可以看到一个人在等待另一个人完成。

Are the Debug and Release builds running at the same time? If so, I could see one waiting for the other to finish.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文