Re-sync status with VC Provider

[ChrisBD]

I have been told that this function is pretty dangerous and should be avoided for EA 7.5 especially if you are using a version control system reliant on the SCC interface, such as ClearCase.

Can anyone enlighten me as to what the problem is whether it is fixed for 8.0?

[Eve]

All it does is update the information in the model about what is checked out and to who based on what is in the VC system.

The potential danger here is that if EA has been allowing edits on a package that wasn't actually checked out it could lock it and when the latest was retrieved again they could be lost.  On the other hand, if you didn't do it, the check-in operation would probably fail.

[ChrisBD]

Thanks for the response.
I've since been informed that there is a peculiarity with the way in which ClearCase works and that is what is causing problems. I have not been able to verify this myself.
Basically an individual user has a configured view of the ClearCase repository so that they see files that they have checked out as checked out and others as locked. They only find out that a package is checked out by another user when they attempt to check it out.
Thus when the Re-synch is run it sets all packages not checked out by the user as locked even those checked out by other users!

Once this has been done, the only means of recovery is to use the ClearCase cleartool application to get a list of packages and there status and then run a script to set the status values in the database.