scm cli how to re-sync a workspace?
We are using the RTC CLI to load multiple versions of a component into RTC3.
Step 1 - share new projects and deliver them to the stream.
Step 2 - perform any updates on existing projects.
We can’t seem to do both steps in the same pass – after adding the new projects, the workspace falls out of synch. As a workaround we remove then recreate/reload the workspace, which is reliable, but slow.
Any tips for performing an in-place synch?
Accepted answer
Load has a switch for force (-f) which will ensure the latest copy is on disk no matter what is checked in. If you are sure that the repository workspace has the best stuff (and not the sandbox), load -force will work.
In terms of the discussion between Tim & Virginia ... if there is some strange behaviour there, we should create a work item to follow up on this.
JohnC
SCM Lead
Comments
Tim Mok
JAZZ DEVELOPER Jan 23 '13, 3:41 p.m.It would be interesting to know what is causing your workspace to become out of sync. It might be the way the projects are being shared. What CLI commands are being run?
Virginia Brown
Jan 24 '13, 7:42 a.m.Tim -
We load the workspace and compare it against the new version, which has been exported to a file system, to determine if there are any new projects. The new projects are shared, checked-in, and delivered. (It's useful to keep the delete/add/update operations atomic in case of failure.)
Tim Mok
JAZZ DEVELOPER Jan 24 '13, 10:27 a.m.How are you sharing the new projects? If you are copying the new projects, there might have been an accidental copy of the metadata from the new version to where you've loaded your workspace. This could cause an out-of-sync situation.