I've just had the joy of discovering a vss bug feature. Basically when you are performing a get latest and a dialog box asks you if you wish to perform an action on a file, while that dialog box is open there is a read-only file lock on a section of VSS that will prevent anybody else from modifying that section.
Due to the way VSS is constructed these sections relate more to the number of versions and changes that they do to the heirachy of files, i.e. the lock was on \\xxxxx\vss\data\g\gcabaaaa. The point here is that while that dialog is open there is a chance that somebody else will be unable to check-in or modify other files.
Of course nobody would have noticed if we didn't have our automated build running, Grrr :) Well done Kais.
This is now fixed again.
---------------------- Done ----------------------
Build: 28 succeeded, 0 failed, 3 skipped
From: Developers
Sent: 20 May 2005 10:12
To: Developers
Subject: xxxxxxxx v2.1 Build - FAILED
Build Failed
Build: xxxxxxxx v2.1
Status: The build did not complete successfully. See the attached output for details.
Project Summary
Succeeded: | 23 |
Failed: | 5 |
Skipped: | 3 |
Project | Errors | Warnings |
xxxxxxxxxxxxx | 0 | 4 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 1 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 0 | 0 |
xxxxxxxxxxxxx | 1 | 0 |
xxxxxxxxxxxxx | 3 | 0 |
xxxxxxxxxxxxx | 4 | 0 |
xxxxxxxxxxxxx | 0 | 2 |
xxxxxxxxxxxxx | 0 | 4 |
xxxxxxxxxxxxx | 21 | 0 |
xxxxxxxxxxxxx | 1 | 0 |