Hudson & Maven

[Greg Akins <an...@gmail.com>]

Looking for advice on configuring Maven/Hudson build and deploying artifacts.

This might be better suited for the Hudson list, but I hoped folks
here might be able to help.

I'm setting up a Maven build in Hudson.  I can use the Maven "deploy"
goal to deploy the artifacts; but Hudson has a "Post-build" task to
deploy artifacts.

Are there pros/cons to doing either?  Or is it a non-issue?  Is anyone
else doing this and do either of the approaches cause problems?

Any advice would be much appreciated.

-- 
Greg Akins

http://insomnia-consulting.org
http://www.pghcodingdojo.org
http://pittjug.dev.java.net
http://twitter.com/akinsgre
http://www.linkedin.com/in/akinsgre

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Hudson & Maven

[Greg Akins <an...@gmail.com>]

On Wed, Aug 18, 2010 at 9:20 AM, Jesse Farinacci <ji...@gmail.com> wrote:
>
> That plugin describes why it exists, and I believe it to be still valid.

Sorry..  I didn't even bother reading the Hudson info beside that plugin.

I'm trying to follow your advice, re: many smaller modules, but this
would help me in the short term on a couple projects.

Thanks for taking the time to explain.

-- 
Greg Akins

http://insomnia-consulting.org
http://www.pghcodingdojo.org
http://pittjug.dev.java.net
http://twitter.com/akinsgre
http://www.linkedin.com/in/akinsgre

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Hudson & Maven

[Jesse Farinacci <ji...@gmail.com>]

Greetings,

On Wed, Aug 18, 2010 at 9:02 AM, Greg Akins <an...@gmail.com> wrote:
>
> I'm setting up a Maven build in Hudson.  I can use the Maven "deploy"
> goal to deploy the artifacts; but Hudson has a "Post-build" task to
> deploy artifacts.

That plugin describes why it exists, and I believe it to be still valid.

> Are there pros/cons to doing either?  Or is it a non-issue?  Is anyone
> else doing this and do either of the approaches cause problems?

I use simple deploy goal but with some additional setup in Hudson
which turns the issue the plugin solves into a non-issue. All of my
multi-module Maven projects are split up using a 1 Hudson job per
Maven module strategy. This lets me achieve high job throughput, high
rates of parallelism using Hudson's own executors, or taking advantage
of slave nodes.

It also is advantageous when you have lots of little in-house
libraries which are used scattershot throughout your modules, in
conjunction with -SNAPSHOT dependencies, additionally in conjuction
with Hudson's build when upstream projects are successful. Since only
what should recompile will, and you'll likely flush out issues quicker
and closer to where they affect downstream.

Lots of little jobs all building quickly gets you status fast. And it
scales quite well.. especially when you combine this with a MRM like
Nexus.

Good luck,
-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org