i update svn repositories daily using svn update command part of batch process. works well, repositories require svn cleanup due lock or conflict. these locks or conflicts removed when run cleanup manually on each repository.
since getting tedious, updated batch process run:
svn cleanup . svn update . i want know if requiring cleanup every time before update practice or not.
having cleanup before update working well, still not sure if effective.
edit: sorry, misstated share working copies. have our own local working copies on our own machines. 1 guy onsite , 2 of offshore.
updates repository done both , onsite guy. update repositories daily since there or other update either onsite or colleague.
i think locking issues due internal subversion locks , not due user locking repositories themselves.
the error used get:
svn_update_2013-5-2-12-25-11.log:21:svn: e155004: 'c:\trunk\decrypt' locked. svn_update_2013-5-2-12-25-11.log:22:svn: run 'svn cleanup' remove locks (type 'svn cleanup' details)
i suggest finding root cause lock , why operations not completed. wrote "i update svn repositories daily" these local working copies or sharing working copies (e.g. on network). might 1 root cause.
update: since confirmed sharing repository via network, suggest read chapter of svn book (make sure read the version corresponds svn version in use). @alroc indicated in comments, each of developers should have own working copy instead of 1 shared via network.
Comments
Post a Comment