Yeah and the last try to resolve anything did not end that well with SF, they claim the problem resides on Team City / Bamboo (as it was at the time) server side.. We get a network time out or something like that..
2009/5/6 Martijn Dashorst <[email protected]>: > On Wed, May 6, 2009 at 1:05 PM, James Carman > <[email protected]> wrote: >> On Wed, May 6, 2009 at 2:53 AM, Johan Compagner <[email protected]> wrote: >>> I very much doubt that it was teamcity that has those problems >>> I think it was the network itself >> >> I'm with Johan on this one. I don't think TeamCity is the source of >> our SVN troubles. Have we contacted infra@ to ask if they see >> anything on their end that would be blocking our TC server? > > The problems with svn don't stem from apache, but rather sf.net. > > It might have been the specific configuration where one svn root was > shared with all projects, which is specific to teamcity. > > Martijn > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.5 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >
