harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess" <mark.hind...@googlemail.com>
Subject Re: classlib build status emails?
Date Tue, 21 Feb 2006 06:52:32 GMT
On 21/02/06, Geir Magnusson Jr <geir@pobox.com> wrote:
>
> Mark Hindess wrote:
> >
> > Hi,
> >
> > Is there any interest in having build status emails sent to this list?
> > I'm building classlib trunk with continuum and it would be simple for
> > me to have messages like the following sent to the list whenever the
> > status of our builds change.  Currently I'm building only on linux but
> > I plan to get windows builds running in the next few days.
>
> Cool.  Please, only send changes (pass->fail, fail->pass).

Agreed.

Done. (Will the non-subscriber nomail@hursley.ibm.com be able to send
to the list or is there something that needs to be done to avoid
moderation/spam filtering?)

> > Currently the builds are running the default target in make/build.xml
> > but if there was a top-level build-and-test target then I could run
> > that instead.  This might produce more useful results.
>
> Ah.  Can you do a sequence :
>
> $ cd make
> $ ant
> $ cd ..
> $ ant -f build-test.xml

The current build is just a direct "svn co" and ant project at
present.  My next step is to use a local repository with svn:externals
pulling in the harmony trunk so I'll have more flexibility.  However,
I suspect more people might run the test target if this process was
simplified.  Of course, as Tim mentioned it's not trivial because of
the requirement for a VM and other dependencies so perhaps it is not
worth it.

I was thinking we might be able to have standard assumptions (encoded
in ant properties) about the location of dependencies and document
setting up the build and test process - much as Tim has done for the
classlib build.  Obviously we'd want a mechanism for overriding the
standard assumptions - perhaps a local (optional) included property
file.

Perhaps once I have setup the test run I'll have a better idea about
how this could be simplified.


I'm going to concentrate on testing first - since the test results are
probably more important than the actual build artifacts at this point
- but wrapping the build should also allow me to add a publish step to
our parent build if there was somewhere I could publish to?

> > On a related note, removing the output attributes from the targets
> > that exec make  (and thus allowing the output to go to stdout/console)
> > would produce much more helpful results and probably result in more
> > constructive bug reports if/when the native builds fail.
>
> Yes indeedy.  I never understood why they were off in a file by default.
>   We've already had one person get confused there...

Thanks.

Regards,
 Mark.

> > ---------- Forwarded message ----------
> > From: Apache Harmony Build <nomail@hursley.ibm.com>
> > Date: 20-Feb-0006 11:04
> > Subject: [continuum] BUILD SUCCESSFUL: Classlib/linux.ia32
> > To: mark.hindess@googlemail.com
> >
> >
> > Online report :
> > http://ibmonly.hursley.ibm.com/continuum/linux.ia32/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/44
> > Build statistics:
> >   State: Ok
> >   Previous State: Failed
> >   Started at: Mon, 20 Feb 2006 11:03:46 +0000
> >   Finished at: Mon, 20 Feb 2006 11:04:56 +0000
> >   Total time: 1m 9s
> >   Build Trigger: Forced
> >   Exit code: 0
> >   Building machine hostname: hy2
> >   Operating system : Linux
> >   Java version : 1.4.2(IBM Corporation)
> >
> > Changes
> >       No files changed
> >
> > ****************************************************************************
> > Output:
> > ****************************************************************************
> > [snip]

--
Mark Hindess <mark.hindess@googlemail.com>
IBM Java Technology Centre, UK.

Mime
View raw message