与 ClearCase 和长期更新快照视图的持续集成
我需要建立一个持续集成系统。由于平台限制，我们使用 ClearCase 版本控制，并且仅使用快照视图。我尝试过设置 Hudson 和 Luntbuild。他们都表现出相同的行为。从某种意义上说，我们有很多用于构建的库，但它们是严格只读的。 CI 系统执行cleartool lshistory 并发现VCS 中的更改。之后，它执行cleartool setcs，这会导致视图更新。这可能需要大约半个小时，这对于 CI 来说是非常不可取的。为什么它不只更新先前由cleartool lshistory 获取的已更改元素？有没有 CI 系统可以做到这一点？
I need to set up a continuous integration system. We use ClearCase version control and only snapshot views due to platform restrictions. I have tried setting up Hudson and Luntbuild. They both show the same behaviour. In a view, we have lots of libraries that are used for build but are strictly read-only. The CI system executes cleartool lshistory and finds a change in the VCS. After that, it executes cleartool setcs, which causes update of the view. This can take about half an hour, which is very undesirable for CI. Why wouldn't it update only the changed elements, which were previously obtained by cleartool lshistory? Is there a CI system that can do this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
更新包含大量元素的快照视图可能需要时间。
这就是为什么我们在 Hudson CI 中使用多个视图。
其他解决方案是，特别是对于第一个视图，使用动态视图（并跳过更新加载时间）
The update of a snapshot view with a lots of elements can takes time.
That is why we are using several view in our Hudson CI.
Other solution is, especially for the first view, to use a dynamic view (and skip the update loading times)
Yulia，
您可以查看我们的 Parabuild -它可能更适合你。如果没有，我们将很乐意与您合作解决任何性能问题。
Yulia,
You may check out our Parabuild - it may work better for you. If not, we will be happy to work with you to resolve any performance issues.