Hi,

one quick note:
Hudson 1.391 doesn't have Maven 3 support, 1.392 will have Maven 3 support (see [1]), and based on the comments to the ticket I would say 1.391 may be a better choice yet, Maven 2 support could show new bugs in 1.392. Mike, I think if you set the build to poll SCM like @hourly , then that should be sufficient too.

Regards,
Peter

[1]: http://issues.hudson-ci.org/browse/HUDSON-4988

2010-12-31 14:39 keltezéssel, Michael O'Cleirigh írta:
Hello,

I've installed the Git plugin on the wicketstuff.org Hudson server. To
use it requires Hudson to be restarted.

I hope that an upgrade to the latest Hudson can be done at the same
time. I think just replacing the war with the version
here(http://hudson-ci.org/latest/hudson.war) and then restarting will work.

There is a Fresh Ports version here (http://www.freshports.org/www/hudson/)

Also the Git Plugin depends on the box itself having git installed. The
latest versions are in the 1.7.x series and the Fresh Ports page is
here: http://www.freshports.org/devel/git

Once Hudson restarted I will adjust the jobs to pull and build from
github and also look into using post commit hooks to notify Hudson when
changes are committed.

Thanks,

Mike

Reply via email to