Hi Tim! I had similar issues with SVN, when using parallel builds (but thereI had been about 15 queues though). After some builds most of our sources were locked and ccnet was unable to update sources unless someone manually done cleanup. We still hadn't time to investigate why did it happen, but I suppose there is a problem with externals pinned to our project's repositories, or problem with multiple requests done by same user.
However if you use Git, maybe you should use two different user accounts, one per build queue? Or there could be some warning or prompt when two projects try to get same sources? I don't even know if it has something to do with Your problem, because i have not much experience with git + ccnet, but maybe it has :) Sincerely, Bartek On 12 Gru, 22:28, Tim Schmidt <[email protected]> wrote: > We're using Git with most of our projects. Since we now have 27 projects > on our build server, we wanted to split them into 2 build queues to cut > down build wait time. However, after making that change earlier today, > we've had continual problems with ssh.exe processes (and therefore the > git.exe process that spawned it) hanging. It seems to happen randomly and > I can't figure out why. Is there possibly a race condition somewhere? > When this problem happens, it completely hangs ccnet until I smack the > offending ssh.exe. I tried upgrading to the latest version of msysgit > (1.7.8) but that didn't seem to change anything. > > For the time being, we'll probably have to go back to a single build queue > since the problem didn't seem to happen then. > > Has anyone seen this or know of anything we can try? > > Thanks, > tim
