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
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
Hi,
If anyone is looking for a Wicket contract position in Edinburgh please
get in contact.
Best regards,
Steven
Steven Tierney
Bright Purple Resourcing Ltd
Senior Consultant
The Eagle Building, 19 Rose Street, Edinburgh, EH2 2PR
Office: +44 131 473 7045 (Direct Line)
+44 131
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
- Hudson can start several runners (i.e. build several projects at once)
while TC agent can build at most one project at a time
Just to keep the facts straight: at my company we have several TC agents
on one machine. Works without problems.
Regards,
Erik.
Op 21-07-10 09:31, Martin
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
martijn.dasho...@gmail.com wrote:
My little bird told me that no build server is part of the new deal
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 jcompag...@gmail.com wrote:
hudson is
This will give you a rough idea of what you need for Hudson. It does
need some disk space:
http://wiki.hudson-ci.org/display/HUDSON/Administering+Hudson
On Wed, Jul 21, 2010 at 8:51 AM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
Security needs to be enabled and other stuff. Deploying
how do you deploy then?
has hudson its container (tomcat)??
Then we also need another port. And have all kind of apache config to
support things like:
wicketstuff.org/hudson
hmm that i dont like. It should just run on the tomcat instance we have.
On Wed, Jul 21, 2010 at 14:51, Martijn Dashorst
Here are the instructions for setting it up on linux/unix:
http://wiki.hudson-ci.org/display/HUDSON/Installing+Hudson#InstallingHudson-Unix%2FLinuxInstallation
You *can* just do:
java -jar hudson.war
and it'll run. That's just a quick way to get it up and running to
play around with it.
On
its a FreeBSD server, so dont know if that is all the same that a linux one.
But still everywhere i see java -jar hudson.war or hudson start
That means that hudson has its own web container right? Where does
that run on? which port?
Then again also changes to apache must be done to map
which is possible, but we should ensure that pranksters won't be
shutting down our server...
Martijn
On Wed, Jul 21, 2010 at 3:58 PM, Johan Compagner jcompag...@gmail.com wrote:
its a FreeBSD server, so dont know if that is all the same that a linux one.
But still everywhere i see java -jar
In linux I've been using the screen command like this:
screen java -jar hudson.war --httpPort=9090
Then detaching and letting it run. Running it like this is useful if
auto update doesn't work and a manual restart is required.
Google seems to show that the 'screen' command also exists for
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
14 matches
Mail list logo
