delivery from stream A to stream B --guidance neededconfused
I was trying to do a merge from stream A to stream B as suggested in other thread. This is what i did
1. create workspace on stream A which as component A 2. Modified the file compA/test.java 3. checked in the file and delivered 4. verfied the history and it shows the changeset Now i want to deliver the same changes set to stream B. so here is what i did 1. changed the flow target from pending change view of stream A workspace to Stream B 2. as soon as i changed the flow target i see incomming changeset in steam A workspace which i used above 3. I went ahead and accepted all the incomming changes 4. changed the flowtarget from stream B to stream A a)My question is did i did the right thing ? b)How can i verify that once i changed the stream flow and accepted all the changes means it was delivered to stream B It confused me a lot can someone please clarify. |
5 answers
Hi,
Basically, you did it correctly. So the changes in A should also be in B. Are you certain that you saw "Incoming Changes" in Step 2 under the second section below? (Where you wanted to deliver the changes). When we do this, using steps similar to what you did, we see "Outgoing Changes" to be delivered. I was trying to do a merge from stream A to stream B as suggested in other thread. This is what i did |
It sounds like you've accepted changes from stream B into your workspace instead of delivering the changes from stream A to stream B. Did you see outgoing changes when you changed your flow target to stream B? Those are the changes that you will deliver to stream B. Accepting from stream B means you've accepted changes into your workspace from stream B.
For a check, show the history on the component from the context of stream B. You can do this by finding it in the Team Artifacts view and showing history on the component from the context menu. Or open the stream editor on stream B and show history on the component. The change set history will be displayed and you can check if your change set exists. Alternatively, you can show the history of the component in your workspace and use the context menu on the change set to locate it in stream B. |
|
Yes sorry when i change the flow target it shows as outgoing changes...
But my question is how do we confirm that the changes got delivered to stream B without creating the workspace on stream B ? or we have to create the workscpae to verify that changes went to stream B Hi, I was trying to do a merge from stream A to stream B as suggested in other thread. This is what i did |
|
Hi,
That was an important difference for your first post. "Outgoing Changes" as opposed to "Incoming Changes". Thanks for the clarification. It appears that you did this correctly. No need to create a new workspace (unless you want to). In the current workspace with the Flow Target of Stream B, you can look in the History of the component that you delivered to and verify that the changes that are in Stream A are also in Stream B. Yes sorry when i change the flow target it shows as outgoing changes... Hi, I was trying to do a merge from stream A to stream B as suggested in other thread. This is what i did |
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 14 '11, 11:33 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You've already done all the verification you need to do.
When you accepted all the changes from stream A into your workspace (i.e., the Pending Changes view showed no more incoming changes), then your workspace has all the changes from stream A. When you switched your target to stream B and delivered all the changes from your workspace into stream B (i.e., the Pending Changes view shows no more outgoing changes), then you are guaranteed that stream B now has all the changes from stream A. Cheers, Geoff On 7/14/2011 4:38 PM, mehulnp wrote: Yes sorry when i change the flow target it shows as outgoing |
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.