version-control - 在 Rational Team Concert 中保持不同流中的相同组件同步

Question

我们有一个客户端/服务器项目，其中包含三个组件:

• 客户端
• 服务器
• 基础库

客户端和服务器都引用 BaseLibrary。因此我创建了两个流:

• Server Stream 包含 Server 和 BaseLibrary 组件
• Client Stream 包括 Client 和 BaseLibrary 组件

现在，如果我在一个流中对 BaseLibrary 进行更改，则它们不会出现在另一个流中。有没有办法让组件在不同的流上与 RTC 2 保持同步？

我还尝试为每个其他流设置流量目标，但这似乎没有帮助。

Answer 1

流之间的流目标只是为了帮助您可视化交付/接受流应该发生的位置:它是一个可视化工具，您可以在创建“流程图”时使用。

在 3.0.1 中，您实际上可以 show pending changes from one Stream to another .

现在您可以设置构建定义和 use the post-build Deliver 为了自动从一个流传送到另一个流:

In this scenario "TeamA" still uses the same trigger policy (to ensure anything they deliver has been validated), however now they are only delivering their single component to the "Integration Stream". In this situation there is no "green" stream, and the Release Engineer no longer has to deliver changes to the integration stream since it is now automated.

Also note from the above Figure that the two checkboxes "Add components to deliver if they do not exist in the deliver target" and "Remove components from the deliver target if they do not exist in the build workspace" are NOT checked.
It is recommended to not propagate component additions / deletions to an integration stream via some automated mechanism. The last thing the team would want is to have all other components removed from the integration stream because someone accidentally modified their team's stream.
The adding or removing of components should be done manually by the Release Engineer in these cases.
For example, if the team needs a new component, they should first add it to their stream, and deliver it to the integration stream. They would then modify the "Components to deliver" selection in the "Post-build Deliver" tab to include this new component and have it automatically delivered afterwards