Newbie maven module questions

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Newbie maven module questions

J. Matthew Pryor-2
I am a bit confused about how module support works with maven & hudson.

We have hudson set up for our top level module, which has about 15  
sub modules.

What I want is that any time a change is checked in for a sub-module,  
only that sub-module is rebuilt, then any other modules that depend  
on it should also be rebuilt.

The way we currently have it set up, I seem to have to do a build on  
the top level module to get it to get new changes from SVN.

I have the SVN polling set up on the top-level module for */10 * * *  
* but that doesn't seem to work for sub-modules.

Do I have to set the SVN config for every sub-module?

Do I have to tell it to use svn update rather then checking out the  
whole source set again?

Thanks for any clarifications or pointers to stuff I should have read

Matthew

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Newbie maven module questions

Kohsuke Kawaguchi
Administrator
J. Matthew Pryor wrote:

> I am a bit confused about how module support works with maven & hudson.
>
> We have hudson set up for our top level module, which has about 15  
> sub modules.
>
> What I want is that any time a change is checked in for a sub-module,  
> only that sub-module is rebuilt, then any other modules that depend  
> on it should also be rebuilt.
>
> The way we currently have it set up, I seem to have to do a build on  
> the top level module to get it to get new changes from SVN.
Correct.

I think what you are describing is a very reasonable thing to do, and
Hudson should be able to support this.

The downside of only building changed modules is that it's much harder
to track what builds of modules work with what builds of other modules,
so for that I'm thinking I need to keep both.

There has been some discussion about this in the past, but don't know if
the issue is filed. If you can do so, that would be great.


> I have the SVN polling set up on the top-level module for */10 * * *  
> * but that doesn't seem to work for sub-modules.

SCM checkout only occurs at the top-level, and Hudson doesn't let you
just update one module.

> Do I have to set the SVN config for every sub-module?

No.

> Do I have to tell it to use svn update rather then checking out the  
> whole source set again?

Personally I always use SCM updates, but this setting is orthogonal from
how Hudson builds modules.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Newbie maven module questions

J. Matthew Pryor-2
In reply to this post by J. Matthew Pryor-2
Here 'tis

https://hudson.dev.java.net/issues/show_bug.cgi?id=532

Thanks for considering it

Matthew

On 01/05/2007, at 11:24 AM, Kohsuke Kawaguchi wrote:



> J. Matthew Pryor wrote:
>
>
>> I am a bit confused about how module support works with maven &
>> hudson.
>> We have hudson set up for our top level module, which has about
>> 15  sub modules.
>> What I want is that any time a change is checked in for a sub-
>> module,  only that sub-module is rebuilt, then any other modules
>> that depend  on it should also be rebuilt.
>> The way we currently have it set up, I seem to have to do a build
>> on  the top level module to get it to get new changes from SVN.
>>
>>
>
> Correct.
>
> I think what you are describing is a very reasonable thing to do,
> and Hudson should be able to support this.
>
> The downside of only building changed modules is that it's much
> harder to track what builds of modules work with what builds of
> other modules, so for that I'm thinking I need to keep both.
>
> There has been some discussion about this in the past, but don't
> know if the issue is filed. If you can do so, that would be great.
>
>
>
>
>> I have the SVN polling set up on the top-level module for */10 * *
>> *  * but that doesn't seem to work for sub-modules.
>>
>>
>
> SCM checkout only occurs at the top-level, and Hudson doesn't let
> you just update one module.
>
>
>
>> Do I have to set the SVN config for every sub-module?
>>
>>
>
> No.
>
>
>
>> Do I have to tell it to use svn update rather then checking out
>> the  whole source set again?
>>
>>
>
> Personally I always use SCM updates, but this setting is orthogonal
> from how Hudson builds modules.
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]