You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@any23.apache.org by Lewis John Mcgibbney <le...@gmail.com> on 2013/01/20 18:30:06 UTC
Jenkins Builds
Hi,
Two questions
- does anyone know why we seem to be running unstable builds most of the
time? This may just be Jenkins...
- does anyone know why the builds attempt iteratively to build various
modules?
Lewis
--
*Lewis*
Re: Jenkins Builds
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Nice one Peter.
As I commented on ANY23-26, I'm running builds just now and we can monitor
things until we get them right.
Also big +1 for bumping revisions to 0.8.0
Lewis
On Sun, Jan 20, 2013 at 2:49 PM, Peter Ansell <an...@gmail.com>wrote:
> On 21 January 2013 08:37, Peter Ansell <an...@gmail.com> wrote:
> > On 21 January 2013 03:30, Lewis John Mcgibbney
> > <le...@gmail.com> wrote:
> >> Hi,
> >> Two questions
> >> - does anyone know why we seem to be running unstable builds most of the
> >> time? This may just be Jenkins...
> >
> > See my other email. Most of our unstable builds that I have
> > investigated turned out to be transient HTTP errors from the test
> > sites that we use to verify compatibility with some real world
> > applications. It shouldn't be too difficult to setup a Jetty web
> > server for integration tests.
> >
> >> - does anyone know why the builds attempt iteratively to build various
> >> modules?
> >
> > The integration tests are performed in a slightly strange manner, that
> > may have been necessary in the past, but I don't think is necessary
> > with Maven-2.2+ or Maven-3.0+. They are performed using the
> > maven-invoker-plugin that boots up a separate copy of maven using a
> > different pom.xml file as the base file for the reactor on the
> > separate copy. This may cause maven to attempt to build things
> > multiple times.
> >
> > Jenkins on the other hand, may be setup to run the build and ignore
> > failures until the end of the build, which will attempt to compile
> > apache-any23-core, even though apache-any23-mime failed to build. That
> > failure to build apache-any23-mime successfully may mean that it was
> > not deployed, and the apache-any23-core build may be using an out of
> > date copy.
> >
> > I managed to get the apache-any23-mime tests to fail on my machine
> > using your combined patches, where it doesn't fail on my tika-1.2 or
> > spi-extractors branches separately. I will investigate what parts of
> > the patch are missing that should still be there and hopefully get a
> > patch for it today.
> >
> > Cheers,
> >
> > Peter
>
> On my branch I had different tika mimetype configuration files to
> allow me to experiment with switching back and forth between tika-0.6
> and tika-1.2 to diagnose test failures. When you checked in the
> patches you checked in some updates to
> mime/src/main/resources/org/apache/any23/mime/mimetypes.xml without
> modifying the filename in
> mime/src/main/resources/org/apache/any23/mime/tika-config.xml. As you
> were working with my patches locally, using subversion, you may have
> been able to successfully ignore the addition of the
> mime/src/main/resources/org/apache/any23/mime/any23-tika-1.2-mimetypes.xml
> file without deleting it, which made the patch work locally and made
> it break after you checked it in. I will submit a patch to subversion
> to correct that file reference after I verify that the tests all work
> after the change.
>
> Cheers,
>
> Peter
>
--
*Lewis*
Re: Jenkins Builds
Posted by Peter Ansell <an...@gmail.com>.
On 21 January 2013 08:37, Peter Ansell <an...@gmail.com> wrote:
> On 21 January 2013 03:30, Lewis John Mcgibbney
> <le...@gmail.com> wrote:
>> Hi,
>> Two questions
>> - does anyone know why we seem to be running unstable builds most of the
>> time? This may just be Jenkins...
>
> See my other email. Most of our unstable builds that I have
> investigated turned out to be transient HTTP errors from the test
> sites that we use to verify compatibility with some real world
> applications. It shouldn't be too difficult to setup a Jetty web
> server for integration tests.
>
>> - does anyone know why the builds attempt iteratively to build various
>> modules?
>
> The integration tests are performed in a slightly strange manner, that
> may have been necessary in the past, but I don't think is necessary
> with Maven-2.2+ or Maven-3.0+. They are performed using the
> maven-invoker-plugin that boots up a separate copy of maven using a
> different pom.xml file as the base file for the reactor on the
> separate copy. This may cause maven to attempt to build things
> multiple times.
>
> Jenkins on the other hand, may be setup to run the build and ignore
> failures until the end of the build, which will attempt to compile
> apache-any23-core, even though apache-any23-mime failed to build. That
> failure to build apache-any23-mime successfully may mean that it was
> not deployed, and the apache-any23-core build may be using an out of
> date copy.
>
> I managed to get the apache-any23-mime tests to fail on my machine
> using your combined patches, where it doesn't fail on my tika-1.2 or
> spi-extractors branches separately. I will investigate what parts of
> the patch are missing that should still be there and hopefully get a
> patch for it today.
>
> Cheers,
>
> Peter
On my branch I had different tika mimetype configuration files to
allow me to experiment with switching back and forth between tika-0.6
and tika-1.2 to diagnose test failures. When you checked in the
patches you checked in some updates to
mime/src/main/resources/org/apache/any23/mime/mimetypes.xml without
modifying the filename in
mime/src/main/resources/org/apache/any23/mime/tika-config.xml. As you
were working with my patches locally, using subversion, you may have
been able to successfully ignore the addition of the
mime/src/main/resources/org/apache/any23/mime/any23-tika-1.2-mimetypes.xml
file without deleting it, which made the patch work locally and made
it break after you checked it in. I will submit a patch to subversion
to correct that file reference after I verify that the tests all work
after the change.
Cheers,
Peter
Re: Jenkins Builds
Posted by Peter Ansell <an...@gmail.com>.
On 21 January 2013 03:30, Lewis John Mcgibbney
<le...@gmail.com> wrote:
> Hi,
> Two questions
> - does anyone know why we seem to be running unstable builds most of the
> time? This may just be Jenkins...
See my other email. Most of our unstable builds that I have
investigated turned out to be transient HTTP errors from the test
sites that we use to verify compatibility with some real world
applications. It shouldn't be too difficult to setup a Jetty web
server for integration tests.
> - does anyone know why the builds attempt iteratively to build various
> modules?
The integration tests are performed in a slightly strange manner, that
may have been necessary in the past, but I don't think is necessary
with Maven-2.2+ or Maven-3.0+. They are performed using the
maven-invoker-plugin that boots up a separate copy of maven using a
different pom.xml file as the base file for the reactor on the
separate copy. This may cause maven to attempt to build things
multiple times.
Jenkins on the other hand, may be setup to run the build and ignore
failures until the end of the build, which will attempt to compile
apache-any23-core, even though apache-any23-mime failed to build. That
failure to build apache-any23-mime successfully may mean that it was
not deployed, and the apache-any23-core build may be using an out of
date copy.
I managed to get the apache-any23-mime tests to fail on my machine
using your combined patches, where it doesn't fail on my tika-1.2 or
spi-extractors branches separately. I will investigate what parts of
the patch are missing that should still be there and hopefully get a
patch for it today.
Cheers,
Peter