Several of the core committers have teamcity running in the company. That is enough reason for me to use that (myself, Maurice (but we work at the same company), Igor, Frank).
The server feels light weight, so I see no apparent reason to switch. Teamcity is secure out-of-the-box. I tried configuring hudson to become secure (i.e. asking for a password but that didn't work). The problem with configuring teamcity has everything to do with the environment where it is deployed, not with teamcity itself. Martijn On 5/3/08, Gwyn Evans <[EMAIL PROTECTED]> wrote: > I'd suggest having a look at getting at least one project running > under Hudson, just so you've got a comparison. I've used it locally > in the past & found it nice & easy, but not for a while now - > It's still the one I'd try first, though. > > /Gwyn > > On Sat, May 3, 2008 at 1:21 AM, Martijn Dashorst > > <[EMAIL PROTECTED]> wrote: > > > Status: > > > > - build server: teamcity professional, is operational, will ask for > > an open source license if we decide to go with teamcity > > - confluence: upgraded to 2.8, operational > > - wicket examples (dojo, 12, 13, security, inmethod): operational > > - teatime operational (##wicket logs) > > - jira - not operational, doesn't want to start up, fails with > > classdef not found > > > > Before we open up the flood gates to all projects to setup team city, > > I'd like to get some opinions first. > > > > Since we currently have 20 or so accounts, I'd like to get some > > volunteers to setup a couple of projects and see how the server > > behaves with more projects. > > > > Martijn > > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
