Delivering to 2 streams simultaneously

We do something similar using "Flow Targets". As an example, for a particular project, we have one "workspace" that is used for builds. Sometimes, we want to "isolate" changes made by the development team and get them delivered into a separate stream than the normal stream that is used for the builds. Then we build with just those changes (using the appropriate build definition, of course). The use of Flow Targets allows us to do this. It is not very hard to do.


Does this sound sort of like what you want to do? If so, let me know and I can explain it in more detail.

- Walter

My team (and every team I know of) has exactly this concern. Our current SCM tool allows us to establish links between the same file in different streams (releases). This link indicates that the files are identical, and when the user delivers the change to one stream he must either deliver them to all linked streams (simply by listing the other streams in a text box) or explicitly break the link.

Right now it appears that switching from our current SCM tool to RTC would force each developer to explicitly manage these relationships. This can more than double the cost of the deliver, as the number of streams is not limited to one each for development and maintenance. It also seems to increase the likelihood of a file falling incorrectly out of sync between various streams.

We are willing to work to make the transition (to RTC) possible (I'm told it may be possible to create a pre or post action that compares the file across streams and potentially performs the deliver in those other streams), but if there is a supported/suggested method, I'd very much appreciate being made aware of it.

I have 2 streams: DevStream (Development), and MainStream (Maintenance) + there are two users: DevUser (DevStream User) and MainUser (MainStream User)

Is it possible to configure these two streams in a way that:
- when MainUser delivers change sets to MainStream, the change sets also appear in DevStream,
- but, when DevUser delivers change sets to DevStream, the change sets don't show up in MainStream?

Is it doable in RTC to deliver a change set to two streams at the same time? If yes, what about conflicts resolution?

You can set up your workspace with all the flow targets that the workspace should flow to. In Pending Changes view, you can switch it to "all flows" mode. When delivering, you can deliver to all the flow targets easily this way. However, it may be a little confusing because components are shown multiple times in Pending Changes (once for every flow target) so you can potentially deliver to a subset of the flow targets.

There isn't an automated way of doing it though. It wouldn't be guaranteed that change sets will apply cleanly to one stream when it depends on change sets from the other stream.

Switching to "all flows" mode requires additional work for guys from maintanance. The usecase was that they deliver to their stream and development stream. If one of them delivers to component "A" from maintenance stream, and forgets to deliver to component "A" from development stream, the streams become unsynchronized and even nobody knows that something bad happenned.