Security

(public)

User Story

Kubla maintains three tags of mozilla.com (trunk, stage, and production). stage and production are updated on cron jobs every 7-15 minutes (not sure of the exact numbers).
Lastely kublad has been tripping over itself and we are getting a lot of "working copy locked" errors. This happens when an SVN process is already messing with the working copy when another process tries to do something.
Updating takes so long (often several minutes per tag) that it seems like the copy is locked more often than not. When this happens people can't use kubla to make changes.
I'm not familiar enough with the setup to make many recommendations but in my experience an `svn up` is essentially disk i/o - are the mozilla.com tags checked out on a local disk (not nfs)? Also, I hear svn 1.5 is faster but I have no proof. It looks like we've been upgraing to 1.5 lately on our other boxes - we should make sure whatever is running kubla is up to date too.