Correct as always. I think Sf were convinced that it was not their problem or something. We actually switched from Bamboo to TeamCity for that reason.. I also created a separate project on google called wicketstuff, but we never could agree on using that instead of sf.
regards Nino 2010/4/1 Igor Vaynberg <igor.vaynb...@gmail.com>: > sf.net keeps banning our TC instance because they think it access svn > too often. nothing we can do about it. i think nino filed a ticket > with them that never got resolved. > > -igor > > On Thu, Apr 1, 2010 at 6:48 AM, Michael O'Cleirigh > <michael.ocleir...@rivulet.ca> wrote: >> Hello, >> >> Recently there has been some initiative in organizing more WicketStuff core >> releases and changes have been going into the sourceforge subversion >> repository for that effect. >> >> But there is a problem with Teamcity not being able to access the >> wicketstuff repository which prevents the updated artifacts being built and >> distributed into the maven snapshot repository. I like to only checkout the >> specific submodules I work on and have m2eclipse resolve the parent from the >> snapshot repository; but that approach doesn't work when the snapshots are >> not being created. >> >> I searched the dev list archive and there was a problem like this in the >> past (Re: TeamCity on wicketstuff.org from November 29 2008). >> >> Here is a link to the build log with the >> '//org.tmatesoft.svn.core.SVNException: svn: connection refused by the >> server'// error: >> http://wicketstuff.org/teamcity/viewLog.html?buildId=5903&tab=buildResultsDiv&buildTypeId=bt35 >> >> It feels like the build server might be blacklisted in some way by >> sourceforge; although it could be something else. >> >> Does anyone know what was done before or have a contact from that time which >> could be used to get teamcity talking subversion again? >> >> Thanks, >> >> Mike >> >> >> >> >> >
