You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Arnaud HERITIER <ah...@gmail.com> on 2008/08/06 23:06:01 UTC
In summer, the sun shines
Hi all,
As you probably noticed I worked on plugins builds.
Benjamin began to cleanup some plugins poms by reordering elements, and
more.
I continued by using everywhere the new maven-parent and maven-plugins
that we will release in few days.
I moved all versions of plugins that we are using in the pluginMgt of the
maven-parent
I standardized the activation of integration-tests profile (skipTests !=
false). It was what we choose on IRC to have this profile activated by
default.
With Benjamin we extracted a lot of integration tests (using embedder,
invoker & co) from unit tests. They are launched in the integration-tests
profile.
And now the sun is shinning in hudson :
https://ci.sonatype.org/view/Plugins/job/Maven-Plugins-ITs/modules
Ok the build takes approximatively 3 hours (and is launched every 4 hours)
which isn't very nice to do continuous integration.
Thus I'm preparing another build without integration tests (
https://ci.sonatype.org/view/Plugins/job/Maven-Plugins-CI/). It requires
maven 2.0.10 to be able to deactivate a profile. I hope to be able to launch
it more oten to have a quick feedback about our changes at least with unit
tests. Actually we have a NPE (
https://ci.sonatype.org/view/Plugins/job/Maven-Plugins-CI/30/console) and
Benjamin thinks that it can be an issue in 2.0.10 :-(
To finish, there were two profile call ci (in maven-parent) and ciProfile
(in maven-plugins) which were used to launch quality checks (cpd and clirr
in maven-parent, docck in maven-plugins). I renamed them quality-checks and
can be activated with quality-checks=true. I schedule a job for that but
certainly with a lower frequency (1 time per week ?).
We are near to be able to release our parents which are now largely
tested. To acheive it, we need to have :
- A release of the modello plugin because the changes report requires a
newest version and we cannot define this one only in this plugin (MNG-3284).
- A release of the enforcer plugin that we use to check that we don't have
in our plugins dependencies : org.codehaus.plexus:plexus-component-api (and
we are waiting for it for a long long time)
- A release of the invoker plugin to fix several issues encountered in ours
integration tests.
What we could do before the release of parents :
- Standardize reports in plugins sites (a lot of them are customizing them
Cheers,
Arnaud
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
Re: In summer, the sun shines
Posted by Arnaud HERITIER <ah...@gmail.com>.
The CI build bypass integration tests.
I don't yet know how many time it makes to build but I think it will be many
more reduced.
On Thu, Aug 7, 2008 at 3:14 AM, Brian E. Fox <br...@reply.infinity.nu>wrote:
> How is the plugin its project different than the one that was already
> there? Why do we need both?
>
> -----Original Message-----
> From: Arnaud HERITIER [mailto:aheritier@gmail.com]
> Sent: Wednesday, August 06, 2008 5:51 PM
> To: Maven Developers List
> Subject: Re: In summer, the sun shines
>
> You're right.
> Before to launch the build, hudson uses the maven embedder to parse the
> project pom (and its modules).
> What I don' understand it's why it's failing each time in CI and not in
> ITS
> whereas it is the same list of modules.
>
> On Wed, Aug 6, 2008 at 11:39 PM, Benjamin Bentmann <
> benjamin.bentmann@udo.edu> wrote:
>
> > Arnaud HERITIER wrote:
> >
> > I think that the memory allocated to hudson isn't really important.
> >> We set memory settings in Maven builds using MAVEN_OPTS.
> >> For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
> >>
> >
> > Well, MAVEN_OPTS is for the *forked* Maven runs. Please have a look at
> > https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console
> > it crashed before Maven ever came into play, it was just doing an
> update
> > from SVN. What is your theory why this build crashed?
> >
> >
> >
> > Benjamin
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
RE: In summer, the sun shines
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
How is the plugin its project different than the one that was already
there? Why do we need both?
-----Original Message-----
From: Arnaud HERITIER [mailto:aheritier@gmail.com]
Sent: Wednesday, August 06, 2008 5:51 PM
To: Maven Developers List
Subject: Re: In summer, the sun shines
You're right.
Before to launch the build, hudson uses the maven embedder to parse the
project pom (and its modules).
What I don' understand it's why it's failing each time in CI and not in
ITS
whereas it is the same list of modules.
On Wed, Aug 6, 2008 at 11:39 PM, Benjamin Bentmann <
benjamin.bentmann@udo.edu> wrote:
> Arnaud HERITIER wrote:
>
> I think that the memory allocated to hudson isn't really important.
>> We set memory settings in Maven builds using MAVEN_OPTS.
>> For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
>>
>
> Well, MAVEN_OPTS is for the *forked* Maven runs. Please have a look at
> https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console
> it crashed before Maven ever came into play, it was just doing an
update
> from SVN. What is your theory why this build crashed?
>
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: In summer, the sun shines
Posted by Jason van Zyl <ja...@maven.org>.
The machine was just put in the rack for builds and it has 32gb RAM so
we can go to the next level.
On 6-Aug-08, at 2:51 PM, Arnaud HERITIER wrote:
> You're right.
> Before to launch the build, hudson uses the maven embedder to parse
> the
> project pom (and its modules).
> What I don' understand it's why it's failing each time in CI and not
> in ITS
> whereas it is the same list of modules.
>
> On Wed, Aug 6, 2008 at 11:39 PM, Benjamin Bentmann <
> benjamin.bentmann@udo.edu> wrote:
>
>> Arnaud HERITIER wrote:
>>
>> I think that the memory allocated to hudson isn't really important.
>>> We set memory settings in Maven builds using MAVEN_OPTS.
>>> For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
>>>
>>
>> Well, MAVEN_OPTS is for the *forked* Maven runs. Please have a look
>> at
>> https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console
>> it crashed before Maven ever came into play, it was just doing an
>> update
>> from SVN. What is your theory why this build crashed?
>>
>>
>>
>> Benjamin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: In summer, the sun shines
Posted by Arnaud HERITIER <ah...@gmail.com>.
You're right.
Before to launch the build, hudson uses the maven embedder to parse the
project pom (and its modules).
What I don' understand it's why it's failing each time in CI and not in ITS
whereas it is the same list of modules.
On Wed, Aug 6, 2008 at 11:39 PM, Benjamin Bentmann <
benjamin.bentmann@udo.edu> wrote:
> Arnaud HERITIER wrote:
>
> I think that the memory allocated to hudson isn't really important.
>> We set memory settings in Maven builds using MAVEN_OPTS.
>> For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
>>
>
> Well, MAVEN_OPTS is for the *forked* Maven runs. Please have a look at
> https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console
> it crashed before Maven ever came into play, it was just doing an update
> from SVN. What is your theory why this build crashed?
>
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
RE: In summer, the sun shines
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Jason was talking about a new box we have. It will be running Vmware ESX
and hosting many VMs to build out a Hudson grid of various os's in
master-slave mode. The current ci.sonatype.org is not on that server but
will be once it's ready.
-----Original Message-----
From: Dan Tran [mailto:dantran@gmail.com]
Sent: Wednesday, August 06, 2008 10:11 PM
To: Maven Developers List
Subject: Re: In summer, the sun shines
how many instances of Hudsons do you install on that box? 32x3? :-)
On Wed, Aug 6, 2008 at 6:13 PM, Brian E. Fox <br...@reply.infinity.nu>
wrote:
> I bumped up the memory for Hudson from 192m to 384m.
>
> -----Original Message-----
> From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
> Sent: Wednesday, August 06, 2008 5:39 PM
> To: Maven Developers List
> Subject: Re: In summer, the sun shines
>
> Arnaud HERITIER wrote:
>
>> I think that the memory allocated to hudson isn't really important.
>> We set memory settings in Maven builds using MAVEN_OPTS.
>> For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
>
> Well, MAVEN_OPTS is for the *forked* Maven runs. Please have a look at
> https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console
> it crashed before Maven ever came into play, it was just doing an
update
>
> from SVN. What is your theory why this build crashed?
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: In summer, the sun shines
Posted by Dan Tran <da...@gmail.com>.
how many instances of Hudsons do you install on that box? 32x3? :-)
On Wed, Aug 6, 2008 at 6:13 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> I bumped up the memory for Hudson from 192m to 384m.
>
> -----Original Message-----
> From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
> Sent: Wednesday, August 06, 2008 5:39 PM
> To: Maven Developers List
> Subject: Re: In summer, the sun shines
>
> Arnaud HERITIER wrote:
>
>> I think that the memory allocated to hudson isn't really important.
>> We set memory settings in Maven builds using MAVEN_OPTS.
>> For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
>
> Well, MAVEN_OPTS is for the *forked* Maven runs. Please have a look at
> https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console
> it crashed before Maven ever came into play, it was just doing an update
>
> from SVN. What is your theory why this build crashed?
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: In summer, the sun shines
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I bumped up the memory for Hudson from 192m to 384m.
-----Original Message-----
From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
Sent: Wednesday, August 06, 2008 5:39 PM
To: Maven Developers List
Subject: Re: In summer, the sun shines
Arnaud HERITIER wrote:
> I think that the memory allocated to hudson isn't really important.
> We set memory settings in Maven builds using MAVEN_OPTS.
> For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
Well, MAVEN_OPTS is for the *forked* Maven runs. Please have a look at
https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console
it crashed before Maven ever came into play, it was just doing an update
from SVN. What is your theory why this build crashed?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: In summer, the sun shines
Posted by Benjamin Bentmann <be...@udo.edu>.
Arnaud HERITIER wrote:
> I think that the memory allocated to hudson isn't really important.
> We set memory settings in Maven builds using MAVEN_OPTS.
> For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
Well, MAVEN_OPTS is for the *forked* Maven runs. Please have a look at
https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console
it crashed before Maven ever came into play, it was just doing an update
from SVN. What is your theory why this build crashed?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: In summer, the sun shines
Posted by Arnaud HERITIER <ah...@gmail.com>.
I think that the memory allocated to hudson isn't really important.
We set memory settings in Maven builds using MAVEN_OPTS.
For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
Arnaud
On Wed, Aug 6, 2008 at 11:22 PM, Benjamin Bentmann <
benjamin.bentmann@udo.edu> wrote:
> Arnaud HERITIER wrote:
>
> Ok the build takes approximatively 3 hours (and is launched every 4
>> hours)
>> which isn't very nice to do continuous integration.
>>
>
> Sure, Brian told me that Hudson was not a dedicated machine but I still
> wonder whether this long build time is normal. For instance, both
> https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console and
> https://ci.sonatype.org/job/Maven-Plugins-ITs/178/console
> crashed during startup with an OutOfMemoryError. In particular, #179
> reported "GC overhead limit exceeded".
>
> Also,
> https://ci.sonatype.org/job/maven-shared/204/
> took only 4 minutes, while the last one
> https://ci.sonatype.org/job/maven-shared/210/
> took 12 minutes.
>
> Can it be that Hudson's JVM is running low on memory and as a consequence
> spends lots of time doing GC to reclaim the few bytes is has, occasionally
> failing as reported?
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
Re: In summer, the sun shines
Posted by Benjamin Bentmann <be...@udo.edu>.
Arnaud HERITIER wrote:
> Ok the build takes approximatively 3 hours (and is launched every 4 hours)
> which isn't very nice to do continuous integration.
Sure, Brian told me that Hudson was not a dedicated machine but I still
wonder whether this long build time is normal. For instance, both
https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console and
https://ci.sonatype.org/job/Maven-Plugins-ITs/178/console
crashed during startup with an OutOfMemoryError. In particular, #179
reported "GC overhead limit exceeded".
Also,
https://ci.sonatype.org/job/maven-shared/204/
took only 4 minutes, while the last one
https://ci.sonatype.org/job/maven-shared/210/
took 12 minutes.
Can it be that Hudson's JVM is running low on memory and as a
consequence spends lots of time doing GC to reclaim the few bytes is
has, occasionally failing as reported?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org