I've searched the forums and found that the "Obliterate" capabilities of the product are suffering and very frustrating to most everyone that uses it.
I just loaded Vault, played for about 5 minutes branching, etc. and now I have files I will never be able to get out of my source control system. I've read all the posts, and none of them truly apply/work. I have deleted and Obliterated all my branches (which was very hard to find I might add). What I have left is a few lonely folders that just won't die.
Thus far, I like Vault. What I don't like is how Obliterate has been implemented and tested. I have been able to complete break the UI getting scripting errors in the HTML pages to the extent I simply had to kill the browser. The error messages generated do not list the projects as they were crafted to. I'm getting the impression that Obliterate is not recursive as it should be.
Mr. and Mrs. Vault, please fix this soon. I'm now very scared to ever branch my code base (thousands of files!) in fear I make a mistake and can not Delete and Obliterate the branch.
Obliterate issues...
Moderator: SourceGear
What are the errors you are getting when you try to obliterate those remaining folders?
Have you checked your Vault Server Log for errors?
Have you checked your Vault Server Log for errors?
-
integradev
- Posts: 8
- Joined: Fri Jan 18, 2008 4:34 pm
Unable to Obliterate item: $/Iwilldeletelater/quicktests/Properties
All branches of an item must be obliterated before the item itself can be obliterated. It is possible that some of the branched items have been deleted, but not obliterated. You must obliterate all branches before you can obliterate this item. This item has branches at:
-- No items listed.
All branches were previously Deleted and Obliterated. Nothing, and I do mean Nothing, remains other than this folder. As you can see, by the depth of the folder above, this was a very simple test on my part to get use to Vault.
Please tell me that your Feb. release will have a fabulous new Obliteration method.
All branches of an item must be obliterated before the item itself can be obliterated. It is possible that some of the branched items have been deleted, but not obliterated. You must obliterate all branches before you can obliterate this item. This item has branches at:
-- No items listed.
All branches were previously Deleted and Obliterated. Nothing, and I do mean Nothing, remains other than this folder. As you can see, by the depth of the folder above, this was a very simple test on my part to get use to Vault.
Please tell me that your Feb. release will have a fabulous new Obliteration method.
An item is not listed, because it's an item that has been deleted. I don't have any cases of it reporting a branch that didn't exists, so somewhere in your deleted items there should be another branch.
What you could do is undelete the folder you are trying to obliterate, and then show history and filter by the branch action to see a list of branching done. Then you will have a list of all the items branched from it to go by and look for in the delete area of obliterate to get that one obliterated first and then delete the problem folder again and obliterate.
I don't have a time line currently on changes to obliterate, but I have added a note from this forum thread to it and included you as an additional vote for changes.
What you could do is undelete the folder you are trying to obliterate, and then show history and filter by the branch action to see a list of branching done. Then you will have a list of all the items branched from it to go by and look for in the delete area of obliterate to get that one obliterated first and then delete the problem folder again and obliterate.
I don't have a time line currently on changes to obliterate, but I have added a note from this forum thread to it and included you as an additional vote for changes.
-
integradev
- Posts: 8
- Joined: Fri Jan 18, 2008 4:34 pm
Thanks for the info Beth.
I've done what you've asked twice now. Once before I posted and then again today. There is nothing to be found. I have two sub-folders; it would be hard to miss. In addition, the History is straight forward.
I'm sure I have found a bug.
To help your development team fix this issue, is there something I can send your way? A history report, listing of a table, etc.? If so, let me know.
Again, all items under my play tree have been Obliterated. The only ones remaining are now undeleted and sitting there getting fat. There are no other Deleted items causing grief. There are no other branches to be found that have not already be Obliterated. There is only two folders and some file, it would be hard for me to miss anything using the History and Properties of each. Would you like me to send the History from the root problem folder?
I've done what you've asked twice now. Once before I posted and then again today. There is nothing to be found. I have two sub-folders; it would be hard to miss. In addition, the History is straight forward.
I'm sure I have found a bug.
To help your development team fix this issue, is there something I can send your way? A history report, listing of a table, etc.? If so, let me know.
Again, all items under my play tree have been Obliterated. The only ones remaining are now undeleted and sitting there getting fat. There are no other Deleted items causing grief. There are no other branches to be found that have not already be Obliterated. There is only two folders and some file, it would be hard for me to miss anything using the History and Properties of each. Would you like me to send the History from the root problem folder?