Revert Vs. Copy&Paste From Edition ON Y:

Tob

Hello,

Last Friday we submitted a bunch of files to STAGING. These files were then deployed to our production Web environment. Later we determined that we needed to revert them back these files to the previous edition. In the interest of Time the quickest way for me to do this was to File Deploy from the Previously Cut Editon (We have a custom File Deploy Solution) to production.

Now I need to revert all those files back in staging to their previous Edition. One way I can do this is to....

1. Do a View -> History on each file I need to Revert.
2. Revert Each File Back to the Previous Edition.
3. Submit to staging.

However, this takes time. Are there any implications with me just doing the following....
1. Go to the Y:
2. Open up the folder of the edition I would like to revert all my files back to
3. Copy and Paste all these files Into my WORKAREA.
4. Submit to Staging.


I wasn't sure is the above method would increase the size of my backing store or not. I predict that METHOD 1 is more efficient because the REVERT feature changes a pointer where as METHOD 2 creates a new version of the file.

james1

If you revert a file from version 5 to version 2, then version 6 should be equal to version 2. i.e., if you compare the file in staging (after your revert-and-submit) to the file in the edition you reverted to, then TeamSite should say that the files are the same.

Using your Method 1, the TeamSite comparisons will be aware of this equality. Using your Method 2, TeamSite comparisons will not be aware.

Instead of reverting files one-by-one in the UI, you could also use the iwrevert CLT (you could write a script to revert all of them for you ... using the UI on a very large set of files could be laborious), or you could use the iwupdate CLT (with overwrite) to update the entire workarea, or entire directories, or individual files.

-- James

--
James H Koh
Interwoven Engineering