need help grouping multiple file chgs together for rollback

[joconnell]

I have the following scenario.

A large number of files are checked out across multiple folders and then they get checked back into Vault.
At some point I find that these files need to be rolled back to the prior version.

Is there a way to group these changes together so that
1) they can be easily found.
2) that they can be rolled back to the prior version as one group.

Jim....

[lbauer]

Is this something you need do on a regular basis or is this a one-time issue?

Once you rollback, do you need to edit the rolled back version or do you need the rolled back version just temporarily and then you will edit the version you rolled back from?

[joconnell]

This is something that unfortunately we need to do on more than an occasional basis.
We get patches to software from our vendor, that we find will have a problem and need to be rolled back out, unitl fixes come from the vendor to fix the patches. These patches usually contain a large number of files.

When we rollback to the prior version, the prior version could possibly need to get modified at a later date.

The version that was determined to be bad, we do not have any need to keep. It is the good version that we rolled back to, which was the last good version is the one we keep and need to be able to modify in the future.

Jim

[lbauer]

There are a couple of ways you might be able to deal with this.

You could use PIN. To pin an earlier version of a file: Show history on the file, right-click on the the version you need and select PIN.


To pin an entire file, right click on the folder and select Show History. In the History Query dialog, select View folder history by version. This will give you a list of versions with their dates. Select the version that corresponds to the date you want, and click on Pin from the buttons on the right.

The pinned version now becomes the latest version. When you do a Get Latest, you will get the pinned version.

Then when you get the updated files, you can unpin and edit as you need to.

Another option is to use Labels. You can apply a label on the version of the file or folder, then test. If the version isn't good, then get that label on the good version or rollback to a label.

Rolling back a folder or label:
http://support.sourcegear.com/viewtopic ... 13&t=12594

[joconnell]

The labeling option is closer to what we need.
But the problem is that the labels need to go on individual files inside a folder and across multiple folders for one patch.

The label process works well for identifying these files across multiple folders, but when rolling back the files,
it seems that I have to do them one at a time. I would like to be able to roll them all back in one step.
Doing it one file at a time can lead to missing a file.

Jim

[lbauer]

There's no easy way to do this in Vault.

Something else to experiment with:

It's possible to label individual files in different folders with the same label, then use the GETLABEL command in the Vault Command Line Client to get that label. You could get to a non-working folder or to the working folder.

The Command Line Client is in the Vault GUI Client directory and is called vault.exe.
Documentation here:
http://download.sourcegear.com/misc/vau ... nt/clc.htm
Examples of commands here:
http://support.sourcegear.com/viewtopic ... 13&t=15235

The downside is if you get to the working folder, the status will now be Old, and you can't check in an Old file. You'd still need to copy the file to a different location, check out the file, then replace it with the labeled version, which makes Vault think the file has been edited.

Perhaps you can automate your process a little more with the Command Line Client.