Jazz SCM持续集成

Jazz SCM持续集成 - 构建流与工作区？(Jazz SCM Continuous Integration - build stream vs. workspace?)

我正在使用Rational Team Concert（RTC）IDE和Jazz构建引擎为Spring Roo应用程序建立持续集成构建。 设置构建定义时，Jazz Source Control选项卡上的Build Workspace字段允许选择用户的存储库工作空间或流。

RTC持续集成最佳实践和其他Jazz构建资源一致地指使用与构建用户关联的专用存储库工作空间，这使我相信这是首选方法。 我无法直接从流中找到有关构建的任何信息。 我们项目的流包含构建所需的所有工件，并且我已经测试并确认了持续集成构建从流中工作。 我无法想到为什么我需要为此目的创建和管理特定工作区。

我的问题是，我是通过直接建立在溪流旁边玩火吗？ 我不知道这种方法是否存在潜在的下游并发症？

I am in the process of setting up a continuous integration build for a Spring Roo application using the Rational Team Concert (RTC) IDE and Jazz build engine. When setting up the build definition, the Build Workspace field on the Jazz Source Control tab allows the selection of either a user's repository workspace or a stream.

The RTC Continuous Integration Best Practices and other Jazz build resources consistently refer to using a dedicated repository workspace associated with a build user, leading me to believe that this is the preferred approach. I have not been able to find any information on building from the stream directly. Our project's stream contains all of the artifacts required to build, and I have tested and confirmed that the continuous integration build works from the stream. I am unable to think of any reason why I would need to create and manage a specific workspace for this purpose.

My question is, am I playing with fire by building directly off of the stream? Are there potential downstream complications with this approach that I am not aware of?

最满意答案

如果另一个SO用户将来有相同的问题，请回答我自己的问题。

经过一些实验，我发现直接从流构建的一个缺点是它忽略了“Jazz Source Control”选项卡上的“仅在接受更改时构建”属性。 因此，流中的构建只能以预定义的时间间隔完成 - 只有在将新的更改提交到流时才能将构建配置为仅进行。

构建需要一个专用工作区来接受来自流的新更改，并使用它们来触发构建请求。

Answering my own question in case another SO user has the same question in the future.

After some experimentation, I discovered that a drawback to building directly from the stream was that it ignores the "Build only if there are changes accepted" property on the Jazz Source Control tab. As a result, builds from a stream may only be done at predefined intervals - it is not possible to configure the build to only happen when new changes have been committed to the stream.

A dedicated workspace is required for the build to accept new changes from the stream and use them to trigger a build request.