Is it expected to have missing changesets shown from other baselines of a component as well while accepting changesets from a different flow target in RTC?
There are 2 streams - Stream A and Stream B and there is a shared component Component C.Stream A needs some bug fixes of Component C from Stream B and hence the flow target in a repository workspace of Stream A is changed to stream B for the component C.Now as expected many incoming changesets are shown but some of them do not belong to the included baseline of the component C in stream B,they are shown from other branches as well.Is this behavior intended in RTC while accepting missing changesets?
|
Accepted answer
Ralph Schoon (63.1k●3●36●46)
| answered Jul 18 '18, 2:33 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER This is perfectly normal SCM behavior.
Ramya Mohan selected this answer as the correct answer
|
One other answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 18 '18, 4:10 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER The incoming change sets will all be from stream B (i.e., all of the incoming change sets are in the change set history of stream B). I'm not sure what you meant by "from other branches". Perhaps you meant "from other baselines"? When the RTC Pending Changes view shows incoming change sets, it groups them according to which baseline those change sets were introduced ... so if you see baselines A, B, and C (in age increasing order) in the pending changes view, the baseline C actually contains all the change sets in B, and baseline B actually contains all the change sets in A, but the Pending Changes view will show under A just the incoming change sets that were first introduced in A, and under B just the incoming change sets that were first introduced in B, etc. |
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.