Re: How can I tell Hudson to build the modules instead of the jobs?

2010-12-10 Thread Andreas Wederbrand
That box doesn't do what I need. Sure, only changed modules get built
(in the same build I might add) but it also makes all other jobs that
have dependencies to any of the modules downstream jobs so commiting
any change to any module will force a complete rebuild of all
dependent modules (and not just dependent on the changed module).

I'll try the hudson list, perhaps it's better there.


On Fri, Dec 10, 2010 at 16:31, Laird Nelson  wrote:
> On Fri, Dec 10, 2010 at 10:12 AM, Wayne Fay  wrote:
>
>> > Sure, that will work but I was hoping for some kind of setting in
>> > hudson or the job "treat modules as jobs" or "treat this job's modules
>> > as jobs".
>>
>> In that case, wouldn't this conversation be more productive on the
>> Hudson Users mailing list rather than Maven Users??
>>
>
> Goodness.  Andreas, there's a checkbox in the Hudson configuration that says
> "Build only changed modules".  That will probably do what you want.
>
> Best,
> Laird
>



-- 
Read my blog @ http://www.raven.nu/blog

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



Re: How can I tell Hudson to build the modules instead of the jobs?

2010-12-10 Thread Laird Nelson
On Fri, Dec 10, 2010 at 10:12 AM, Wayne Fay  wrote:

> > Sure, that will work but I was hoping for some kind of setting in
> > hudson or the job "treat modules as jobs" or "treat this job's modules
> > as jobs".
>
> In that case, wouldn't this conversation be more productive on the
> Hudson Users mailing list rather than Maven Users??
>

Goodness.  Andreas, there's a checkbox in the Hudson configuration that says
"Build only changed modules".  That will probably do what you want.

Best,
Laird


Re: How can I tell Hudson to build the modules instead of the jobs?

2010-12-10 Thread Wayne Fay
> Sure, that will work but I was hoping for some kind of setting in
> hudson or the job "treat modules as jobs" or "treat this job's modules
> as jobs".

In that case, wouldn't this conversation be more productive on the
Hudson Users mailing list rather than Maven Users??

Wayne

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



Re: How can I tell Hudson to build the modules instead of the jobs?

2010-12-10 Thread Andreas Wederbrand
Sure, that will work but I was hoping for some kind of setting in
hudson or the job "treat modules as jobs" or "treat this job's modules
as jobs".

On Fri, Dec 10, 2010 at 10:48, Asmann, Roland  wrote:
> How about configuring a single job to check-out and build just one
> module? Would mean that you have lots of jobs (probably one for every
> module), but that way the big job wouldn't need to be triggered (don't
> forget to turn of polling and the subversion-hook!).
>
> Then you could run the big job at night or something like that...
>
> Roland
>
> On 10-12-10 09:20, Andreas Wederbrand wrote:
>> Hi!
>>
>> I have a alot of jobs on Hudson, most of which are really small and
>> consist of just a few modules. But one is big and consist of several
>> modules.
>>
>> When ever I make a commit to our subversion repository for any of
>> those several modules in that big job, Hudson builds the entire job
>> instead of just the module that have changed.
>>
>> It doesn't matter if I just scm-polling or a subversion hook, the
>> result is the same.
>>
>> It seems to me like it would be better if the modules where built
>> instead of the jobs since the other modules in other jobs have
>> dependencies to the modules and not to the jobs.
>>
>> Can this be configured or do I have to create several jobs instead of
>> the big one? And if so, can I configure the big job to never build
>> when any of it's modules are being triggered but still build when it's
>> own pom.xml is changed?
>>
>> Thanks.
>>
>> --
>> Read my blog @ http://www.raven.nu/blog
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>
> --
> Roland Asmann
> Senior Software Engineer
>
> adesso Austria GmbH
> Floridotower 26. Stock              T +43 1 2198790-27
> Floridsdorfer Hauptstr. 1           F +43 1 2198790-927
> A-1210 Wien                         M +43 664 88657566
>                                    E roland.asm...@adesso.at
>                                    W www.adesso.at
>
> -
>             >>> business. people. technology. <<<
> -
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Read my blog @ http://www.raven.nu/blog

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



Re: How can I tell Hudson to build the modules instead of the jobs?

2010-12-10 Thread Asmann, Roland
How about configuring a single job to check-out and build just one 
module? Would mean that you have lots of jobs (probably one for every 
module), but that way the big job wouldn't need to be triggered (don't 
forget to turn of polling and the subversion-hook!).

Then you could run the big job at night or something like that...

Roland

On 10-12-10 09:20, Andreas Wederbrand wrote:
> Hi!
>
> I have a alot of jobs on Hudson, most of which are really small and
> consist of just a few modules. But one is big and consist of several
> modules.
>
> When ever I make a commit to our subversion repository for any of
> those several modules in that big job, Hudson builds the entire job
> instead of just the module that have changed.
>
> It doesn't matter if I just scm-polling or a subversion hook, the
> result is the same.
>
> It seems to me like it would be better if the modules where built
> instead of the jobs since the other modules in other jobs have
> dependencies to the modules and not to the jobs.
>
> Can this be configured or do I have to create several jobs instead of
> the big one? And if so, can I configure the big job to never build
> when any of it's modules are being triggered but still build when it's
> own pom.xml is changed?
>
> Thanks.
>
> --
> Read my blog @ http://www.raven.nu/blog
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

-- 
Roland Asmann
Senior Software Engineer

adesso Austria GmbH
Floridotower 26. Stock  T +43 1 2198790-27
Floridsdorfer Hauptstr. 1   F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at

-
 >>> business. people. technology. <<<
-

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



How can I tell Hudson to build the modules instead of the jobs?

2010-12-10 Thread Andreas Wederbrand
Hi!

I have a alot of jobs on Hudson, most of which are really small and
consist of just a few modules. But one is big and consist of several
modules.

When ever I make a commit to our subversion repository for any of
those several modules in that big job, Hudson builds the entire job
instead of just the module that have changed.

It doesn't matter if I just scm-polling or a subversion hook, the
result is the same.

It seems to me like it would be better if the modules where built
instead of the jobs since the other modules in other jobs have
dependencies to the modules and not to the jobs.

Can this be configured or do I have to create several jobs instead of
the big one? And if so, can I configure the big job to never build
when any of it's modules are being triggered but still build when it's
own pom.xml is changed?

Thanks.

--
Read my blog @ http://www.raven.nu/blog

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