On Sun, Jan 23, 2011 at 11:10 PM, Benson Margulies
wrote:
> OK, then, if you give me a patch, I'll see if my long-dormant karma is
> effective, at least in getting some attention.
My proposed patch is probably not something you want in Hudson (in
there, the algorithm for rebuilding the dependency
OK, then, if you give me a patch, I'll see if my long-dormant karma is
effective, at least in getting some attention.
On Sun, Jan 23, 2011 at 2:33 PM, Niklas Gustavsson wrote:
> On Sun, Jan 23, 2011 at 6:21 PM, Benson Margulies
> wrote:
>> I'm a very rusty hudson dev. So I'm reduced to the foll
On Sun, Jan 23, 2011 at 6:21 PM, Benson Margulies wrote:
> I'm a very rusty hudson dev. So I'm reduced to the following question:
> do we really need interjob hudson dependencies at Apache (the
> downstream/upstream business).
Yes, they are used quite a lot. And, it would seem that testing
depend
Benson,
Right now, when there is a change in Axiom, Hudson will also trigger
builds of Neethi, Woden, Axis2, Sandesha2 and Rampart. This is what we
want because it allows us to ensure non-regression in downstream
projects. This relies on Hudson calculating the dependencies
automatically. Disabling
Niklas,
I'm a very rusty hudson dev. So I'm reduced to the following question:
do we really need interjob hudson dependencies at Apache (the
downstream/upstream business). If all the jobs are set to turn this
off, does it still calculate?
Another view of this would be to look to splitting up huds
Hi
Some of you might have noticed that Hudson can take a long time on
Maven builds in the step called "Parsing POMs". In fact, some builds
will time-out due to this step taking 15 minutes or more. Thing is, as
part of this step, Hudson will do the problematic rebuild of its
dependency graph. This
