How to restrict the flow target (between streams) to make sure the flow happens in only on direction?
![]() Hiya there, I'm new RTC, but have started to like the tool. I'm in a dilema. I'll explain my scenario. I've 2 streams, StreamA and StreamB 2 different team have created workspace and connected to their respective streams and started their work. I've created a flow target in StreamA to StreamB. I want the changes to move from StreamA to StreamB and not the otherwise. The problem i'm facing is that when i created the flow target, from A to B, the changes delivered to the streamB is also coming into StreamA Now in the pending changes view, StreamA <-> StreamB item, if the same file present in incoming and outgoing, I'm not able to do either and not able to merge as well. I want a way to restrict the flow of code so that code can move only from StreamA to StreamB. Is there any way to do this in RTC? Thanks, Venkit |
2 answers
![]()
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/160738 - It sounds like you want directed flows. This is currently not supported but there is a story item describing what you want.
The ability to show a stream in your Pending Changes view only allows for accept and deliver actions. There is no support to perform merges so you'll have to do that by using a repository workspace. Once you've resolved conflicts in the repository workspace, you can deliver the changes to the stream. http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.team.scm.doc/topics/t_flow_changes_to_stream.html - It's also mentioned in the documentation that only non-conflicting flows are supported in stream-to-stream flows. Comments Hi Tim, This info saved me a lot of time. So ideally if developers need to check in to both the streamsA and StreamB, thne they'd have to do it manually. Connect to the first one and checkin and deliver and connect to the StreamB and resolve any conflicts and checkin and deliver. hmm... i guess there is no other way that can be used for the problem at hand. Thanks mate Yes, you'll have to deliver using a workspace to both streams. Although, you've seen that streams can be tracked in Pending Changes and allows delivery. My team uses this for flowing changes between our team stream and integration stream. It's not as useful if you're trying to flow changes from a current release stream to an older release stream where the code has diverged, which may cause conflicts.
|
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.