Eelco Hillenius wrote: >> You _must_ do this in association with the Apache Infrastructure group. >> >> The ASF's repository is large. There have been occasions when FishEye >> has put the ASF SVN server under an unnecessary load. >> >> It _should_ be possible, but _must_ be done in consultation with the >> infrastructure team. > > I am a little bit suprised tbh. We're talking about a site than checks > every once in a while for new updates. Maybe it generates the load > that would normally be generated by a couple of users. Did this really > gave Apache problems in the past? Others, like Codehaus, Rife or > sourceforge with us in the past don't seem to have any problems with > it...
It isn't the ongoing usage that is the problem - it is the initial usage. When you set it up (which I have done), it first scans the entire history in your SVN repository. (This is configurable though). And for typical Apache projects, this can create huge loads that can make SVN unresponsive to other users (it certainly has in the past). I do believe Cenqua have done stuff so that Fisheye is more polite. However, I still would not support setting up Fisheye against an Apache SVN without infrastructure's support as they are the ones that would have to pick up the pieces if it were to go wrong. That need be little more than an email and wait for a response. So not necessarily onerous. Regards, Upayavira ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
