We have recently begun to experience problems with "locks" on our cvs server since we began using teamcity. We're getting messages from our "legacy" nightly build process as follows:
cvs rtag: waiting for abc's lock in /cvsara/modules/ara/webapps/ara/WEB-INF/res/regression/response
The "legacy" build process puts a tag on the cvs module every build. Now the teamcity build is running as user abc, but as far as I gather, teamcity doesn't modify the cvs module. Is that correct?
If so, I'm not sure why it creates a lock, especially based on reading this:
Is there anything teamcity is doing while monitoring a sandbox for changes that might create a lock on the cvs server?