Security needs to be enabled and other stuff. Deploying as a war does have some drawbacks: restarting using the UI won't work, installing/updating plugins/new versions of hudson is enabled by default.
Martijn On Wed, Jul 21, 2010 at 2:46 PM, Johan Compagner <[email protected]> wrote: > hudson is just a war right? > so that can be dumped by anybody of the wicket devs to onto the tomcat > webapp dir. > > What more does hudson need? > > > On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst > <[email protected]> wrote: >> My little bird told me that no build server is part of the new deal >> which is slated to be announced mid-august, so IMO we should not delay >> the migration off of teamcity and setup hudson. I'll contact the >> sysadmin for the box to see if I can grant direct access, or that only >> "trusted" folks are allowed. >> >> Martijn >> >> On Wed, Jul 21, 2010 at 9:43 AM, Martijn Dashorst >> <[email protected]> wrote: >>> There are some developments unfolding in the near future that might >>> help out on the future of our wicketstuff server and/or its >>> infrastructure. I don't have the full details to those plans yet, and >>> don't know if they entail a build server of some sorts. >>> >>> I'm perfectly happy with switching to hudson—we use it at work and it >>> has been a godsend compared to the other available solutions (though I >>> still don't like the UI). >>> >>> I hope we can wait a (couple of) week(s) and see the future plans >>> unfold to see what the details are, especially with respect to a build >>> server. I'll ask around to see if it is part of that deal. >>> >>> Martijn >>> >>> On Wed, Jul 21, 2010 at 4:06 AM, Michael O'Cleirigh >>> <[email protected]> wrote: >>>> 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 >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Become a Wicket expert, learn from the best: http://wicketinaction.com >>> Apache Wicket 1.4 increases type safety for web applications >>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.4 increases type safety for web applications >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 >> > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
