How can I revert repository workspace back in time?
Lauren Hayward Schaefer (3.3k●1●17●27)
| asked May 19 '15, 6:50 a.m.
JAZZ DEVELOPER edited May 19 '15, 6:52 a.m.
I have created a repository workspace for a stream. The stream has years of history before the first baseline was created (initially the code was in a CVS repo, so all of the CVS history exists prior to the baseline). How can I create/revert a repository workspace so that it is back in time to the initial delivery?
|
4 answers
Ralph Schoon (63.1k●3●36●46)
| answered May 19 '15, 7:42 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Several things to mention here.
If you want to bring a workspace into a certain state, you can
If you have data on a stream that you want on top of that workspace state, you can accept it in.
Comments Hi Ralph,
Ralph Schoon
commented May 19 '15, 7:55 a.m.
| edited May 19 '15, 7:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The pending changes DOES show the difference of its state and the state of the stream. If you discard from the workspace, the data is not there any more. If it is still in the stream, you get it as incoming.
The CVS import is a bit tricky, can you look at the history of a stream that has the imported components on it? Do you see baselines? There is a good article about the import and you have to play with it a bit to get it right and especially to get the baselines imported.
For some reason when I discard changests from the CVS import, they don't show up in Incoming. They just disappear.
|
If you only want a single change set from the beginning of time, you can:
1. replace the component with the component's initial baseline.
2. load the repo workspace into your sandbox. (haha! it's empty, so nothing is going to happen! we're using this to get the workspace into your Pending Changes view)
3. find the change set (either on a work item, or in the history of the stream), then run "accept" from the context menu.
Comments What is strange about my case is that the initial baseline is dated in 2013. However, the repo has history from years prior to 2013 as it was migrated from CVS.
Suspending the changesets from the history view works. It's just surprising that discarding the changesets doesn't work.
Geoffrey Clemm
commented May 22 '15, 6:22 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Performing a "suspend" should be identical to performing a "discard", except that in addition to discarding the change set, the change set is also added to the "suspended" list. If that is not what you are seeing, then it sounds like a bug to me, and should be reported. If you'd like to screen share sometime next week, so I can take a look, just let me know.
|
|
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.
Comments
I tried discarding changesets from my workspace as described in https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.scm.doc/topics/t_discarding_change_set.html&scope=null. The changesets created after the team started using RTC appear in my Incoming changes. However, the changesets created by converting from the CVS repo's history are not appearing in Incoming changes. Does the Pending Changes view only display changesets created after the first baseline?
Update: I can suspend the changesets that were created by converting from the CVS repo's history and they are listed in the Pending Changes view under suspended. Any ideas why RTC would know how to suspend but not discard these changes?