Reverse changeset
I'm trying to clarify the Reverse functionality in RTC as the docs are not quite clear. From the user manual, this is done from the users repo workspace - show history and select the changeset to "Reverse". In the user Pending changes they then get a Pending Patches object to accept. What is actually happening in this process? Our (perhaps incorrect) assumption is that the target stream of the initial delivery would have the change backed out. Does this affect the users dev repo/sandbox? Does this reverse function remove the change from a baselined component ? (Assume that the change was part of the baseline.) Can a reversed changeset be re-delivered?
|
One answer
Martha (Ruby) Andrews (3.0k●4●43●51)
| answered Apr 18 '14, 5:27 p.m.
JAZZ DEVELOPER edited Apr 18 '14, 5:28 p.m.
The Reverse function calculates the changes needed to reverse (undo) the original change and shows those changes as a patch. The user can accept the patch into her repository workspace and deliver the reversal change set to propogate the reversal to the stream. Reversing the change in and of itself does not "undo" anything; it simply creates a new change set. From that point on, the change set is like any other.
Ruby Martha (Ruby) Andrews Team Lead, Jazz Foundation L3 Development |
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.