Procedure to back out a delivered change set
![]()
We have a simple model of Team stream with an associated production
build workspace which accepts all incoming changes, creates a snapshot, and builds. If we want to back out one of change sets delivered to the team stream, and have it available for delivery later on, what is the easiest way to accomplish this? Thanks, Brian |
10 answers
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 21 '09, 1:57 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There are two ways to "back out" a set of change-sets from a stream.
The first is to use the "reverse" operation (as described below by Anthony). This is for a "permanent" removal of that change set. (I put "permanent" in quotes, because you could undo the reversal by applying the "reverse" operation to the reversal change set itself). But this doesn't sound like it is what Brian wanted, because he wants it "available for delivery later on". So I believe Brian wants the other way, which is to: - accept the contents of the stream into a workspace - open the history view of the workspace - select the activities that you want to back out - select the "suspend" operation - use the "replace" operation to replace the content of the stream with the content of your workspace. Cheers, Geoff kesterto wrote: bgillanwrote: |
![]() We have a simple model of Team stream with an associated production Hi I happened to be looking in the help for something completely different - and saw this: " Reversing a change set If you want to undo the delivery of a change set, you can create a new change set that reverses all the changes in it and then deliver the reversed change set. The Reverse operation enables to you to undo a delivery by creating a special change set that, when applied to a flow target, removes the changes made by a change set without removing the change set itself. When you remove a change set from a workspace or stream, it appears as an outgoing change set bearing the original owner and creation date. Reversing a change set accomplishes the same thing as removing it, and avoids this occasionally confusing side effect. Reverse creates a Rational Team Concert source control patch that, when merged into your workspace, removes the changes made in a specific change set (the change set that it was created to reverse) and creates a new change set. You can deliver this change set to reverse those changes in workspace flow targets." See if this helps... anthony |
![]()
Check out the Source Control FAQ: http://jazz.net/library/article/126
"How do I remove a change set from a stream?" describes both methods and what to watch for. There are two ways to "back out" a set of change-sets from a stream. bgillanwrote: |
![]()
I wanted to get the code of a particular date from history. The steps followed to get this
(1) Show Repository Files (From workspace) (2) Show History (3) Show Repository Files (From history) (4) Load But Load fails with the error 'Problem occurred running load wizard. Reason: The load selection contains from mulitple workspace.' I want to get the code of 1st June, 2009. |
![]()
From the history view, open the change in the change explorer (instead of
going to the repository files view in step 3), right click your file and choose Load. It will get the contents of the file at that state (and as a result produce an 'unresolved' local modification change. On Tue, 11 Aug 2009 06:08:04 -0400, pranjan <prabhat> wrote: I wanted to get the code of a particular date from history. The steps -- |
![]()
Thanks Andrew,
I got the files, as you suggested. But there is a limitation in this approach. I had to load every indivisaul file. Is there any way by which I may get the entire code base on one click for any particualr date or version as we can get it in Team Foundation Server (TFS)? I got the files by loading evry files indivisually in the same fashion I have mentioned below. But when I try to get the whole code it shows the error. If possible please intimate me at prabhatranjan@ymail.com if this gets resolved in furture release. Huge thanks once again for your assistance. From the history view, open the change in the change explorer (instead of I wanted to get the code of a particular date from history. The steps -- |
![]()
There is no action to get a batch of files according to a certain date. If
you know ahead of time that a certain date is important, then the recommended workflow is to create a snapshot of the workspace at that time. Then it is much easier to recover your contents from the snapshot. I've filed 89905 to for your use case. On Wed, 12 Aug 2009 05:08:04 -0400, pranjan <prabhat> wrote: Thanks Andrew, -- |
![]()
pranjan wrote:
Is there any way by which I may That question doesn't really make sense for Jazz SCM. Because there are not really branches in the version tree (at least not branches that have names or that can otherwise be identified), there is no way for Jazz SCM to satisfy the request of "Give me the latest version of everything on a particular branch as of a specific time." Simply getting the most recently created version of the file isn't what you want, because the most recently created version may have been part of a different stream that you aren't interested, or may have been in a developer's workspace which was never delivered. The closest you can come to what you want, rephrased in Jazz SCM terminology, is probably "Give me everything that was in a given stream at a specific time." I don't know if Jazz SCM keeps enough information to know what was in a stream at a particular time. As Andrew Hoo said, if you want to go back to a time in the past, you need to baseline or snapshot to go back to. |
![]()
Hello.
Handy pointer to 86931 : "Provide an operation on a workspace that rolls it back to the state it had at a particular date". Indeed this requirement could come in handy. I have a souvenir of easiness to do that with ClearCase. Random timestamp could be used to see a configuration at random time. G. There is no action to get a batch of files according to a certain date. If |
![]()
Thx Pranjan I was looking for this steps for long time. :roll:
|