[DISCUSS] Nightly Jenkins Builds for Trunk

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Nightly Jenkins Builds for Trunk

lewis john mcgibbney
Hi Folks,
Right now in Jenkins (builds.apache.org) we don't seem to have a Tika
project directory which contains the trunk build... it is just a free
standing project burried under the mountain of jobs currently running on
that box.
We also don't build Tika nightly... in fact AFAICT it has been built twice
in the last 30 or so days...
We use latest JDK6... which IMHO is not sufficient as Annie (one of many I
am sure) has recently encountered problems building and testing Tika
against Oracle JDK8.
We don't seem to run tests within the current Trunk Jenkins
configuration!!! We instead look for tasks... if they do not exist we do
not run any tests... IMHO this is a waste of Jenkins resources as the job
is provisioned and very rarely actually used.
We can therefore not view test output if anything goes wrong! Which is not
beneficial to anyone wanting to know current health of trunk.
Does anyone have an issue with me jumping on to the Jenkins job and
bringing it bang up to date with JDK7 (at least), provisioning a new job
for JDK8 until we get this stable and also publishing test output for
reference and review... finally running nightly builds which push nightly
SNAPSHOT's for consumption by developers?
Thanks
Lewis

--
*Lewis*
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Nightly Jenkins Builds for Trunk

Michael McCandless-2
+1 to have a Tika Jenkins job that runs periodically, posts results,
and for separate Java 7/8 runs.


Mike McCandless

http://blog.mikemccandless.com


On Wed, May 14, 2014 at 11:21 AM, Lewis John Mcgibbney
<[hidden email]> wrote:

> Hi Folks,
> Right now in Jenkins (builds.apache.org) we don't seem to have a Tika
> project directory which contains the trunk build... it is just a free
> standing project burried under the mountain of jobs currently running on
> that box.
> We also don't build Tika nightly... in fact AFAICT it has been built twice
> in the last 30 or so days...
> We use latest JDK6... which IMHO is not sufficient as Annie (one of many I
> am sure) has recently encountered problems building and testing Tika
> against Oracle JDK8.
> We don't seem to run tests within the current Trunk Jenkins
> configuration!!! We instead look for tasks... if they do not exist we do
> not run any tests... IMHO this is a waste of Jenkins resources as the job
> is provisioned and very rarely actually used.
> We can therefore not view test output if anything goes wrong! Which is not
> beneficial to anyone wanting to know current health of trunk.
> Does anyone have an issue with me jumping on to the Jenkins job and
> bringing it bang up to date with JDK7 (at least), provisioning a new job
> for JDK8 until we get this stable and also publishing test output for
> reference and review... finally running nightly builds which push nightly
> SNAPSHOT's for consumption by developers?
> Thanks
> Lewis
>
> --
> *Lewis*
Reply | Threaded
Open this post in threaded view
|

RE: [DISCUSS] Nightly Jenkins Builds for Trunk

Allison, Timothy B.
In reply to this post by lewis john mcgibbney
+1 Please, yes.  Thank you!

-----Original Message-----
From: Lewis John Mcgibbney [mailto:[hidden email]]
Sent: Wednesday, May 14, 2014 11:21 AM
To: [hidden email]
Subject: [DISCUSS] Nightly Jenkins Builds for Trunk

Hi Folks,
Right now in Jenkins (builds.apache.org) we don't seem to have a Tika
project directory which contains the trunk build... it is just a free
standing project burried under the mountain of jobs currently running on
that box.
We also don't build Tika nightly... in fact AFAICT it has been built twice
in the last 30 or so days...
We use latest JDK6... which IMHO is not sufficient as Annie (one of many I
am sure) has recently encountered problems building and testing Tika
against Oracle JDK8.
We don't seem to run tests within the current Trunk Jenkins
configuration!!! We instead look for tasks... if they do not exist we do
not run any tests... IMHO this is a waste of Jenkins resources as the job
is provisioned and very rarely actually used.
We can therefore not view test output if anything goes wrong! Which is not
beneficial to anyone wanting to know current health of trunk.
Does anyone have an issue with me jumping on to the Jenkins job and
bringing it bang up to date with JDK7 (at least), provisioning a new job
for JDK8 until we get this stable and also publishing test output for
reference and review... finally running nightly builds which push nightly
SNAPSHOT's for consumption by developers?
Thanks
Lewis

--
*Lewis*
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Nightly Jenkins Builds for Trunk

Nick Burch-2
In reply to this post by lewis john mcgibbney
On Wed, 14 May 2014, Lewis John Mcgibbney wrote:
> Right now in Jenkins (builds.apache.org) we don't seem to have a Tika
> project directory which contains the trunk build... it is just a free
> standing project burried under the mountain of jobs currently running on
> that box.

I believe that Buildbot is the main system being used for testing +
nightly builds - http://ci.apache.org/builders/tika-trunk/

> Does anyone have an issue with me jumping on to the Jenkins job and
> bringing it bang up to date with JDK7 (at least), provisioning a new job
> for JDK8 until we get this stable and also publishing test output for
> reference and review... finally running nightly builds which push nightly
> SNAPSHOT's for consumption by developers?

Can you clarify what we'd get by using Jenkins instead of Buildbot? Is it
easier to manage perhaps? Easier to setup for multiple Java versions?

As for JVM versions, we currently require 1.6, so we need to test on that.
Newer ones would be good too! But we mustn't loose the 1.6 which is our
minimum version...

Nick
Reply | Threaded
Open this post in threaded view
|

RE: [DISCUSS] Nightly Jenkins Builds for Trunk

Hong-Thai Nguyen-2
And for >=Java7, we need a profile to active building 'tika-java7' module.

Hong-Thai

-----Message d'origine-----
De : Nick Burch [mailto:[hidden email]]
Envoyé : mercredi 14 mai 2014 18:30
À : [hidden email]
Objet : Re: [DISCUSS] Nightly Jenkins Builds for Trunk

On Wed, 14 May 2014, Lewis John Mcgibbney wrote:
> Right now in Jenkins (builds.apache.org) we don't seem to have a Tika
> project directory which contains the trunk build... it is just a free
> standing project burried under the mountain of jobs currently running
> on that box.

I believe that Buildbot is the main system being used for testing + nightly builds - http://ci.apache.org/builders/tika-trunk/

> Does anyone have an issue with me jumping on to the Jenkins job and
> bringing it bang up to date with JDK7 (at least), provisioning a new
> job for JDK8 until we get this stable and also publishing test output
> for reference and review... finally running nightly builds which push
> nightly SNAPSHOT's for consumption by developers?

Can you clarify what we'd get by using Jenkins instead of Buildbot? Is it easier to manage perhaps? Easier to setup for multiple Java versions?

As for JVM versions, we currently require 1.6, so we need to test on that.
Newer ones would be good too! But we mustn't loose the 1.6 which is our minimum version...

Nick
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Nightly Jenkins Builds for Trunk

lewis john mcgibbney
In reply to this post by lewis john mcgibbney
Hi Nick/Others,
Please see link below for Tika trunk build on Oracle JDK's (latest) 6 and 7
respectively.
We also have a now deprecated Tika trunk build which was doing zilch... we
also have a currently disabled cob configured to run with Oracle JDK8
(latest) when this become available to build machines via Infra.

@Nick, please see comments to your response. Thank you folks for the
responses.
Lewis

https://builds.apache.org/view/Tika/

On Fri, May 16, 2014 at 8:18 AM, <[hidden email]> wrote:

>
> I believe that Buildbot is the main system being used for testing +
> nightly builds - http://ci.apache.org/builders/tika-trunk/
>

This was also doing nothing. IMHO we could delete this buildbot
configuration as it is wasting resources.


>
> Can you clarify what we'd get by using Jenkins instead of Buildbot? Is it
> easier to manage perhaps? Easier to setup for multiple Java versions?
>

* The jobs are configured at the link I've provided above. They poll the
Tika trunk SVN SCM URL every hour for changes and deploy a job if they
detect revision change to trunk codebase.

* We now will be pushing ONLY stable Tika trunk SNAPSHOT's (currently
1.6-SNAPSHOT's) to
https://repository.apache.org/content/repositories/snapshots/org/apache/tika/certainly
on ever stable build (possibly nightly). This lets Dev's use
cutting edge Tika stuff without having to build locally. You can merely
include SNAPSHOT configuration in your project build if it can consume
Maven artifacts.

 * Jenkins has a real simple REST API meaning that we/I can shift the
script's I've written for automating nightly update and deployment of Any23
service which resides at any23.org over to Tika. This will let users and
developers use a stable SNAPSHOT version of the Tika trunk codebase in a
live Web Application. This is really nice for demo's of new functionality,
etc.

* ... blah blah blah don't want you guys falling as well :)



> As for JVM versions, we currently require 1.6, so we need to test on that.
> Newer ones would be good too! But we mustn't loose the 1.6 which is our
> minimum version...
>
> please see above... thank you. Have a great weekend folks.
Lewis