Hudson：同一存储库上的多个作业
它看起来像 我如何设置 Hudson 为不同的项目使用相同的存储库并维护单独的更改日志？ 但事实并非如此。
就我而言，情况略有不同：
Trunk
-----项目 1
-----项目 2
-----项目 3
-----公共库
公共库包含项目之间的共享库。现在，出于同样的原因，我正在为每个项目设置一个单独的作业：独立报告（java doc、测试结果等）
有没有办法防止每个作业都有自己的存储库警察（从 SCM 检出）？
我想我可以压缩存储库并在下一个项目中提取，但我希望还有其他东西。我怀疑这是一个独特的设置。
It looks like How can I setup Hudson to use the same repository for different projects and maintain separate change logs? but is not.
In my case the scenario is a little bit different:
Trunk
-----Project 1
-----Project 2
-----Project 3
-----Common Libraries
Common Libraries contains shared libraries among the projects. Right now I'm setting each project a separate job for the same reasons: independent reporting (java doc, test results, etc)
Is there a way to prevent each job have their own cop of the repository (checked out from SCM)?
I guess I can zip the repository and extract in the next project but I hope there's something else in place. I doubt this is an unique setup.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
仅检查每个项目使用的内容，以便您只有多个库，但没有项目。如果您使用 Subversion，则可以添加任意数量的 Subversion 位置，而无需使用多个 scm 插件。在一份工作中，我有近 20 个不同的工作地点。
如何配置更多位置？
配置第一个位置。在页面的右侧（在“本地模块目录（可选）”和“签出策略”之间）有一个按钮“添加更多位置...”，这将为您提供另一个“存储库 URL”字段来输入第二个位置。我正在使用 Jenkins 1.421 和 Subversion 1.28
Only checkout what is used by each project, so that you only have multiples of the libraries, but not the projects. If you use Subversion, you can add as many subversion locations as you want to without the multiple scm plugin. In one job I have almost 20 different locations.
How to configure more locations?
Configure the first location. On the right side of the page (between "Local module directory (optional)" and "Check-out Strategy") there is a button "Add more locations ..." This will give you another "Repository URL" field to enter a second location. I am using Jenkins 1.421 and Subversion 1.28
您可以为所有三项工作拥有一个共同的工作空间。如果您只需要使用公共库而不需要构建它们，那么只要您为项目（或单独的）文件夹中的每个作业构建了特定信息（以及所有临时文件，......），就应该没问题。但是，我不知道当两个作业同时签出/更新代码时是否会发生冲突。
由于硬盘空间很便宜，我会给每个作业它自己的空间（包括它自己的公共库）。如果您担心 svn 服务器超载，那么只需运行更新而不是完全签出。
you can have a common workspace for all three job's. If you only need to use the common libraries and not build them, you should be fine as long as you have build specific information (and all the temporary files, ....) for each job in the project (or separate) folder. However, I don't know if it can come to conflicts when two jobs checkout/update code at the same time.
Since HDD space is inexpensive I would give each job it's own space (including it's own common libraries). If you are concerned about overloading the svn server, than just run an update instead of complete checkout.
经过一番思考后，我认为最好的方法是使用多 SCM Hudson 插件并签出项目 1 和仅公共库等等。
After giving it some thought I think the best approach is using the multi SCM Hudson plug-in and checkout Project 1 and the common libraries only and so on.