如何存储程序的依赖项并在 SCC 中测试项目部署？
我正在从 Visual Source Safe 迁移到 SVN，所以请原谅我的无知。 我正在浏览此链接，其中讨论了 SVN 的最佳实践。 我觉得有些事情很奇怪。
SVN 中的第三方软件项目或依赖项的副本是不可接受的
什么？？？ 如果我不在 SVN 中保存依赖项，Team city 应该如何构建我的项目？ 新开发者如何一步步建设？ 我可以在哪里保存测试的一些依赖项（例如项目中包含原始数据的测试子文件夹）。
我是否在某个地方遗漏了一个重要的概念？
I'm migrating from Visual source safe to SVN, so please forgive my ignorance.
I was browsing this link which talk about best practices in SVN. And something seems very wierd to me.
Copies of third party software projects or depedencies in SVN is unacceptable
What ??? How Team city is supposed to build my project if I don't save the dependencies in the SVN ?? How new developpers can build in one step ? Where can I save some depedencies of my tests (like a test subfolder in my project which contains raw data).
Am I missing an important concept somewhere ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我不同意这种说法。 我们将第三方 dll 保留在存储库中，以便构建服务器可以编译项目，而无需我们安装 sdk 或其他软件。
I would disagree with that statement. We keep third-party dlls in our repository so the build server can compile the projects without us having to install sdk's or other software.
这些都是昆士兰大学的“良好做法”。 通读该文档，您会发现他们的存储库有配额。 这可能就是他们不希望存储库中存在第三方二进制文件的原因。 这可能是由于许可证问题（毕竟，他们是一所大学，可能不允许学生使用许可的库）。
对于您的公司，您可以建立自己的“良好/最佳实践”。 将第三方库放入存储库中绝对是允许的，甚至取决于您的设置！
有些公司甚至将所有开发工具都放在存储库中，以确保可以使用相同的编译器/IDE再次构建代码。 但我不建议这样做 - 我宁愿将编译器/IDE 存储在其他地方而不是存储在存储库中。
These are the "good practices" for the Queensland university. Reading through that doc you'll discover that they have a quota for their repositories. That's probably why they don't want third party binaries in the repository. That and maybe due to license problems (after all, they're a university an maybe won't allow students to use licensed libs).
For your company, you can set up your own "good/best practices". Putting third party libs in the repository is definitely allowed and depending on your setup even required!
Some companies even put all the development tools in the repository to ensure that the code can be built again with the same compiler/ide. But I wouldn't recommend that - I'd rather store the compilers/ides somewhere else than in a repository.
我也不同意这个说法。 我认为该声明的背景是它似乎为很多人提供了一个共享存储库，因此管理磁盘配额等是一个主要问题。
根据需要归档依赖项、工具等是一个很好的做法，以确保您可以在需要时重新创建旧的发布/构建环境。
I too disagree with that statement. I think the background context for that statement was that it seemed to be providing a shared repository to a large number of people and so managing disk quotas etc. were a primary concern.
It is a good practice to archive dependencies, tools etc. as necessary to ensure that you can recreate an old release/build environment if needed.