Well, since lowering the interval does not seem to have any effect, I suggest to put it back to once every minute. Probably makes it easier for somebody from sourceforge to diagnose the problem if there is something to diagnose every 60 seconds instead of every hour.
And Nino, thanks for the time you put in this. On Mon, 13 Oct 2008 20:39:10 +0200, "Nino Saturnino Martinez Vazquez Wael" <[EMAIL PROTECTED]> said: > And we should also be able to specify reverse calls going from svn to > teamcity instead... > > Anyhow im in process with sourceforge tecnical support on the svn > issues.. However it's very slow. > > Arnout Engelen wrote: > > On Sun, Oct 12, 2008 at 12:16:09PM +0200, Martijn Dashorst wrote: > > > >> I've lowered it to once every hour, but that does remove any benefit > >> we have from a CI server. > >> > > > > Well, if this means updates will start working again at least it's a big > > improvement - I've had to wait well over a day before my commits came > > though :/. > > > > You'd think there should be some kind of way to subscribe TeamCity to > > a commits-mailinglists and make that trigger updates, removing the need for > > polling... > > > > > > Arnout > > > > > >> Martijn > >> > >> On Sun, Oct 12, 2008 at 11:14 AM, Pointbreak > >> <[EMAIL PROTECTED]> wrote: > >> > >>> Maybe you can also lower the checking interval, to see if that fixes the > >>> VCS problems teamcity has all the time? > >>> > >>> On Fri, 10 Oct 2008 01:15:12 +0200, "Martijn Dashorst" > >>> <[EMAIL PROTECTED]> said: > >>> > >>>> I've just upgraded teamcity from 3.1.1 to 3.1.2. > >>>> > >>>> Martijn > >>>> > >> > >> -- > >> Become a Wicket expert, learn from the best: http://wicketinaction.com > >> Apache Wicket 1.3.4 is released > >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > >> > > -- > -Wicket for love > > Nino Martinez Wael > Java Specialist @ Jayway DK > http://www.jayway.dk > +45 2936 7684 >
