Hi, Recently in my company we moved from TeamCity to Hudson for two major reasons: - Hudson can start several runners (i.e. build several projects at once) while TC agent can build at most one project at a time - Hudson knows Maven, i.e. after building project X it builds all projects that depend on X
We even contributed a tool to Hudson that migrates TC configuration to Hudson one, but I understand you already did that part. So I'm +1 for the change, but I don't have permissions to the box where wicketstuff.org is running. 2010/7/21 Michael O'Cleirigh <michael.ocleir...@rivulet.ca> > Hello, > > I've been using Hudson reliably to build wicketstuff core snapshot's and > deploying them into the sonatype maven repository. I put together an older > machine for this purpose (P4 1.8Ghz) and while it worked at first recently > there have been memory issues (at least one of the DDR1 DIMM's is bad and > the JVM keeps crashing). I have the builds running temporarily somewhere > else but the long term solution is to run Hudson on a box that can be opened > up to the other wicketstuff developers. > > My proposal is to replace TeamCity on wicketstuff.org with Hudson and then > do the necessary setup to allow wicketstuff developers access to it for > initiating builds and viewing the projects status. > > I am willing to do all of the necessary setup and configuration to make > this happen; basically copying over what I have working right now plus > adding in user authentication. > > The easiest way would be if I could get a user account on the > wicketstuff.org server (at least initially) and then get everything setup. > > There are still some questions around if the wicketstuff.org box is still > banned by sourceforge but I think the best way to find out the answer is to > try and see what happens. > > Regards, > > Mike > > > > > > > > > > > > > > > > > > > > > > > > > > >
