Implementing one-way flow targets between streams
Hi All,
I have 2 streams - stream1 and stream2. Stream2 is the flow target for stream1. When i modify the same set of files continuously, changes do flow back from stream2 to stream1 and available in stream1's incoming changes view. But i do not want the changes from stream2 to flow back to stream1 - and it cannot be ignored as a lot of developers work on it and there are chances of merges happening in stream1 as well..
Is there any policy setting to restrict the backward flow and prompting in the incoming changes view?
one solution that i can think of is to have an unused stream in between the two - which is unnecessary storage of duplicate data.
Thanks.
I have 2 streams - stream1 and stream2. Stream2 is the flow target for stream1. When i modify the same set of files continuously, changes do flow back from stream2 to stream1 and available in stream1's incoming changes view. But i do not want the changes from stream2 to flow back to stream1 - and it cannot be ignored as a lot of developers work on it and there are chances of merges happening in stream1 as well..
Is there any policy setting to restrict the backward flow and prompting in the incoming changes view?
one solution that i can think of is to have an unused stream in between the two - which is unnecessary storage of duplicate data.
Thanks.
One answer
This is not currently supported, but there are a variety of work items requesting this functionality, e.g.
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=160738
Feel free to add a comment to this work item indicating your interest/support.
Cheers,
Geoff
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=160738
Feel free to add a comment to this work item indicating your interest/support.
Cheers,
Geoff
Hi All,
I have 2 streams - stream1 and stream2. Stream2 is the flow target for stream1. When i modify the same set of files continuously, changes do flow back from stream2 to stream1 and available in stream1's incoming changes view. But i do not want the changes from stream2 to flow back to stream1 - and it cannot be ignored as a lot of developers work on it and there are chances of merges happening in stream1 as well..
Is there any policy setting to restrict the backward flow and prompting in the incoming changes view?
one solution that i can think of is to have an unused stream in between the two - which is unnecessary storage of duplicate data.
Thanks.