It's all about the answers!

Ask a question

Roll back in RTC


Sean Burke (3789144247) | asked May 01 '13, 7:24 p.m.
edited May 01 '13, 7:30 p.m.
Can you help me with this situation. ...... I change 3 files.  I will probably need to rollback and access those three files.   The three are part of change set.  I also put them as part of a baseline and deliver.  So basically there is a version in production but they have to roll back to the historical revision of a small subset of files in the component..  Any idea on the best way to do this?

From knowing what I know this is what I can think of but maybe I am missing something completely.
  • A baseline is not the rollback solution because  the baseline shows all the files in the component.
  • Is the change set the best way to roll back and bring these files into my sandbox?  If so what is the mechanism?

Thanks........

Accepted answer


permanent link
Josh Crawford (984615) | answered May 01 '13, 8:24 p.m.
 Hi Sean,  if you want to roll back the versions you have delivered you can follow the reversing of the changeset procedure here:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/topic/com.ibm.team.scm.doc/topics/t_reversing_change_set.html?resultof=%22%72%65%76%65%72%73%65%22%20%22%72%65%76%65%72%73%22%20

If you just want to be able to access the previous revisions in your workspace you can always browse the history of the file and just choose to accept the older changeset into your workspace. 
Sean Burke selected this answer as the correct answer

One other answer



permanent link
Geoffrey Clemm (30.1k33035) | answered May 01 '13, 8:27 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The easiest way to roll back a single change set is to use the "reverse" operation on that change set in your workspace.  This creates a new change set that reverses/undoes the changes in the original change set.   Then you deliver that new change set to the stream, and the changes are undone in the stream.

An alternative is to "discard" the change set from your workspace, and then right click on the component in your stream that used to contain the discarded change set, and then use the "replace" operation to replace the configuration of that component in the stream with the configuration of that component in your workspace.

Cheers,
Geoff

Comments
Sean Burke commented May 06 '13, 7:32 p.m. | edited May 06 '13, 7:32 p.m.

Thanks for the reply Geoffrey and Josh, The reverse option does appear the best option but there is a twist.  We may need to roll back to a package of three files and that package consist of an .esql file, a .bar file and a message flow file.  


All three files will initially be part of a change set but the .esql file and the .bar will undergo further revisions.  The message flow  file will stay the same.  So the final revision before deployment will have a change set consisting of only the .esql file and the .bar file and not the message flow file.  The message flow file is not part of the latest change set because it has not been modified.  Is there a way to get this version of file into the latest change set.

Or is there another mechanism to allow for roll back of a three file package?



Geoffrey Clemm commented Jun 09 '13, 3:44 p.m. | edited Jun 09 '13, 3:45 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Not quite sure what is being asked ... let's make the example more explicit.  For example, is the scenario that:

I have change-set-A that creates the three files: foo.esql, foo.bar, and foo.message-flow.  Let's call the state of those three files in change-set-A "foo.esql;1", "foo.bar;1", and "foo.message-flow;1".  I then create a new change-set-B that modifies foo.esql and foo.bar, but does not modify foo.message-flow.  Let's call the state of those two files in change-set-B "foo.esql;2" and "foo.bar;2".  

Assuming that is the scenario (please clarify if it is not), what file states would you like to have in your workspace/stream?

Your answer


Register or to post 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.