1

We're trying to move a bunch of folders from one location to another in our vob. The process is that:

  • we check out the target parent folder
  • check out the source parent parent folder
  • ct mv source target

This unfortunately fails with moving only the top folder in the tree... On the other hand ct relocate works fine and we avoid checking out thousands of vob elements. Are there any drawbacks with that command? We assume that the source and the target are in the same vob.

zeller
  • 4,904
  • 2
  • 22
  • 40

1 Answers1

2

We assume that the source and the target are in the same vob.

Then cleartool mv is enough: see "To move an element within a VOB"

It won't move just the top element.

As mentioned in "Relocating elements to another VOB":

The relocate command does not do any of the following:

  • Relocate elements when either the source or the target VOB is a UCM component VOB or PVOB.
  • Move view-private files and nonversioned DOs stored in relocated directories.
  • Move elements to a new location in the same VOB. (Use cleartool mv for this purpose.)
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • Thanks VonC! The symptom why we think mv is not enough is that after the command, ls in the new location show nothing in the moved folder. Does it mean that we're not working with the same VOB? – zeller Nov 21 '14 at 13:29
  • @zeller or it could means that the content of the source folder wasn't yet added to source control (a `cleartool ls` in the source folder *before* the move can help to see what is going on) – VonC Nov 21 '14 at 13:31
  • they're under version control. So they're in different VOBs and our assumption was bad, no other possibilities right? – zeller Nov 21 '14 at 13:40
  • @zeller if they are in different vobs, then yes, the assumption was incorrect, and `cleartool relocate` is the right tool. – VonC Nov 21 '14 at 13:41