Hi
We recently embarked on a process of renaming files in an MS Analysis Services project wich was under the control of Vault.
Prior to renaming we labelled the entire project directory recursively (all its child folders/files) in Vault to provide us a rollback point.
The IDE & Ananlysis services didn't handle the file renaming well (many internal GUID references became broken when we tried to build the project) so we're attempting to rollback the entire project to the labelled version in Vault but we can't work out how to do this.
Could some please tell me how to achieve this?
Thanks in advance
Project/folder rollback in Vault 5.0.3
Moderator: SourceGear
Re: Project/folder rollback in Vault 5.0.3
Vault doesn't support folder rollback yet, but there is a workaround.
Here's a post with a similar issue:
http://support.sourcegear.com/viewtopic ... 48&t=16411
Here's a post with a similar issue:
http://support.sourcegear.com/viewtopic ... 48&t=16411
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 2
- Joined: Wed Jul 06, 2011 6:31 am
Re: Project/folder rollback in Vault 5.0.3
Hi Thanks for your quick response.
A few points:
1. The work around referred to in the post does not work for us. Our change set was files within the project being renamed - the file content remained unchanged. We tried the work around and it didn't work for us because the "get earlier labelled version" did **not** get a copy of the project as it was at that point time i.e. newly changed file names were not reverted to their previous file names.
If I had done a diff between the latest & pre-renaming labelled version it says there is no difference. I can only assume therefore that Vault only monitors files contents
2. Looking back through the forum I see references to this exact same lack of functionality <SPAM> back to 2004 (!) with promises that it was being impliment in v4.
We're now on v5 and 7 years (!) later on & this functionality still doesn't exist
3. For source control software to not allow rollback at anything other than the individual file level seems quite remarkable to me
In summary I've recommended clients move from VSS to Vault due to the well known issue with VSS. Up until this point I really liked Vault as being right on the button for simplicity, cost, easily adopted by VSS users & far more robust. I know find myself in the embarressing situation of having to explaint to one particualr client why the source control software I recommended they migrate to doesn't actually support rollback.
Which really is quite unbelievable.
I can only assume that Vault has become a victim of its own success and the people who wrote the origional code and started the comapany are no longer hands on involved in the product development because they obviously wrote software to meet a need that they had i.e. a robust, simple replacement for VSS. If they were still writting code they would know importatnt rollback-at-the-project-level is.
Needless to say I will never use Vault on another project and indeed will inform all clients of this lack of functionality & recommend that they do adopt Vault.
A sad day really
Steve
A few points:
1. The work around referred to in the post does not work for us. Our change set was files within the project being renamed - the file content remained unchanged. We tried the work around and it didn't work for us because the "get earlier labelled version" did **not** get a copy of the project as it was at that point time i.e. newly changed file names were not reverted to their previous file names.
If I had done a diff between the latest & pre-renaming labelled version it says there is no difference. I can only assume therefore that Vault only monitors files contents
2. Looking back through the forum I see references to this exact same lack of functionality <SPAM> back to 2004 (!) with promises that it was being impliment in v4.
We're now on v5 and 7 years (!) later on & this functionality still doesn't exist
3. For source control software to not allow rollback at anything other than the individual file level seems quite remarkable to me
In summary I've recommended clients move from VSS to Vault due to the well known issue with VSS. Up until this point I really liked Vault as being right on the button for simplicity, cost, easily adopted by VSS users & far more robust. I know find myself in the embarressing situation of having to explaint to one particualr client why the source control software I recommended they migrate to doesn't actually support rollback.
Which really is quite unbelievable.
I can only assume that Vault has become a victim of its own success and the people who wrote the origional code and started the comapany are no longer hands on involved in the product development because they obviously wrote software to meet a need that they had i.e. a robust, simple replacement for VSS. If they were still writting code they would know importatnt rollback-at-the-project-level is.
Needless to say I will never use Vault on another project and indeed will inform all clients of this lack of functionality & recommend that they do adopt Vault.
A sad day really
Steve
Re: Project/folder rollback in Vault 5.0.3
You're right, the workaround doesn't work that well when there are renames.
Perhaps a better suggestion would be to branch from the label, and then continue work in the branch. That way, you should have the project in the state before the renames.
I know we've had "folder rollback" as a request for some time, but it's a complicated thing to implement. If we rollback, how do we handle renames, shares, deletes, branch operations, obliterates, etc? Rolling back entire changesets can have unexpected results. That might be why VSS doesn't have this feature.
It's true that we've focused on many other important features over the past few years, and we're still mulling over this one. It's still on our to-do list, though.
That being said, I'm concerned about this statement:
If you'd like, we can schedule a remote assist session where I can take a closer look. email support at sourcegear.com, Attn: Linda. Please include a link to this forum post.
Perhaps a better suggestion would be to branch from the label, and then continue work in the branch. That way, you should have the project in the state before the renames.
I know we've had "folder rollback" as a request for some time, but it's a complicated thing to implement. If we rollback, how do we handle renames, shares, deletes, branch operations, obliterates, etc? Rolling back entire changesets can have unexpected results. That might be why VSS doesn't have this feature.
It's true that we've focused on many other important features over the past few years, and we're still mulling over this one. It's still on our to-do list, though.
That being said, I'm concerned about this statement:
The Get Label should get files with the names at the time of the label. Did that not happen? And a diff between the Folder label and the current version in the repository should show file name differences."get earlier labelled version" did **not** get a copy of the project as it was at that point time i.e. newly changed file names were not reverted to their previous file names.
If you'd like, we can schedule a remote assist session where I can take a closer look. email support at sourcegear.com, Attn: Linda. Please include a link to this forum post.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager