Delivering to 2 streams simultaneously
Przemyslaw Bozowski (11●1)
| asked Dec 01 '10, 10:20 a.m.
edited Jun 21 '16, 10:20 a.m. by David Lafreniere (4.8k●7)
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? |
4 answers
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. It's not the exact solution to the use case but at the very least the developer can see that there are outgoing changes to another stream. Pending Changes also has a deliver all out going changes action. With all flows view, the change sets would be delivered to all flow targets with one action. Unfortunately, I think you'll need something custom, using API, to check incoming deliveries to a stream and check if it needs to be delivered to another stream. Although, I think it is good that users have to explicitly deliver to a stream. All the responsibility of knowing what is flowed to a stream is put on the developer and they can handle any merges that may be required when dealing with development and maintenance streams. |
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 03 '10, 12:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A result of this "file linking" feature of some SCM systems is you are
modifying a large number of configurations without ever having seen or tested those configurations. The alternative approach used by RTC makes sure that each owner of a stream can define what are the "deliver conditions" for delivering to that stream, and that no code is delivered to that stream unless those deliver conditions are met. Cheers, Geoff On 12/1/2010 1:08 PM, shonuff wrote: My team (and every team I know of) has exactly this concern. Our |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
As far as I know, this kind of behavior is not supported.
Could you explain your use case?
My team is working on an interim stream, which needs to be synchronized with maintanance stream. We can do this single-handedly by changing flow target of the interim stream to maintenance stream and accept all the change sets. But we wanted to automate this procedure, so when somebody delivers to maintenance stream, the change sets appears in "incoming list" of our interim stream too, so this is our usecase.