交付机制，Rational ClearCase
我们为 Rational ClearCase UCM 模型提出了一个流结构。
Int
-- Prd
-- Uat
-- Dev
---- Development Stream r1.0
我们最近将代码库迁移到新设置中。我们有三个不同的代码库，即三个物理代码库。
迁移过程：
我们首先移动生产代码，创建一个活动，将活动交付到集成流，创建一个基线。
然后，uat 代码创建了一个活动，将该活动交付到集成流，在合并期间，我们选择了贡献者 2 的更改以保留 uat 中的现有代码，创建了基线。 开发环境的过程相同。
截至目前，集成流具有最新的基线，即开发基线。
现在我们有另外两个用于 prd 和 uat 的流，将在各自的环境中完成发布。
我现在有了我的开发流。我创建一个活动并进行一些更改。现在我需要将这些改变推广到uat环境中。如果我将更改交付到集成流，合并就会完成，但会在开发基准上完成。我不想将其重新设置为 uat，因为许多开发应用程序将重新设置为 uat，这是不希望的。
如何实现促进 uat 环境（uat 流）的改变。善意的建议。
We came up with a stream structure for the Rational ClearCase UCM model.
Int
-- Prd
-- Uat
-- Dev
---- Development Stream r1.0
We recently migrated the code base into the new setup. We had three different code bases, i.e. three physical code bases.
Migration process:
We moved the production code first, created an activity,delivered the activity to Integration stream, created a baseline.
Then the uat code, created an activity, delivered the activity to integration stream, during merge we chose the changes from the contributor 2 to preserve the existing code from uat, created a baseline.
The same process for the dev environment.
As of now the integration stream has the latest baseline that is the development baseline.
Now we have other two streams for the prd and the uat from which the release will be done in the respective environments.
I have my dev stream now. I create an activity and make some changes. now I need to promote these changes into the uat environment. If I deliver the changes to the integration stream, merge is done but on a development basline. I do not want to rebase it to uat as many development apps wil get rebased into the uat which is not desired.
How do I achieve promoting changes to the uat environment(uat stream). kindly advice.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
看起来你的流结构是这样的：
流的原理是隔离特定的开发工作：
Int 中记录最新的 Prd 基线，以便允许另一个项目使用这些基线之一作为起点，避免使用由分支的分支组成的基线（“级联分支”）。
我建议（这只是一个建议，许多其他结构也是可能的，具体取决于您需要将一个与另一个隔离的开发工作的确切集合）：
Looks like your stream structure is like this:
The principle of a stream is to isolate a specific development effort:
Int being there to record the latest Prd baseline in order to allow another project to use one of those baselines as starting point, avoiding using a baseline made from a branch of branch of branch ("cascading branching").
I would recommend (and this is only one proposition, many other structures are possible, depending on the exact set of development efforts you need to isolate one from another):