You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Richard Eckart de Castilho <re...@apache.org> on 2013/12/04 13:50:56 UTC

Update Jenkins settings for UIMA-AS?

Hi,

the UIMA-AS job on Jenkins has the following settings which should probably be updated:

1) currently bound to "ubuntu1||ubuntu2" -> suggesting "Ubuntu||Windows"

2) set to use JDK 1.6 (latest) -> suggesting JDK 1.5 (latest)

3) not running code quality plugins (findbugs, etc.) -> suggesting to enable them

Any objections/comments?

-- Richard

Re: Update Jenkins settings for UIMA-AS?

Posted by Richard Eckart de Castilho <re...@apache.org>.
There is one more difference to the other builds: the UIMA-AS SNAPSHOT builds are not deployed to the Apache Nexus. Can we enable this? Any reason why there shouldn't be SNAPSHOT builds deployed to the Apache Nexus?

-- Richard

On 04.12.2013, at 12:31, Richard Eckart de Castilho <re...@apache.org> wrote:

> On 04.12.2013, at 12:26, Jaroslaw Cwiklik <ui...@gmail.com> wrote:
> 
>> Hi Richard,
>> 
>> 1) Does this setting control what platform the UIMA-AS job is deployed on?
> 
> It controls on which kinds of build nodes the Jenkins job can run. Unless there
> are specific requirements for the build environment, this binding should
> be as lax as possible to let Jenkins assign the build to free nodes.
> I suggest "Ubuntu||Windows" because there have been notorious problems with
> some of the other kinds of build nodes, particularly solaris.
> 
> This is just for building the project, not for any kind of deployment.
> 
>> 2) , the latest UIMA-AS requires at least JDK 1.6 starting from release
>> 2.4.2 due to
>> the fact that the ActiveMQ it uses has been compiled with 1.6.
> 
> Ok.
> 
>> 3) Enabling Findbugs plugin is fine with me.
> 
> Ok. Will enable this then.
> 
> -- Richard


Re: Update Jenkins settings for UIMA-AS?

Posted by Richard Eckart de Castilho <re...@apache.org>.
On 04.12.2013, at 12:26, Jaroslaw Cwiklik <ui...@gmail.com> wrote:

> Hi Richard,
> 
> 1) Does this setting control what platform the UIMA-AS job is deployed on?

It controls on which kinds of build nodes the Jenkins job can run. Unless there
are specific requirements for the build environment, this binding should
be as lax as possible to let Jenkins assign the build to free nodes.
I suggest "Ubuntu||Windows" because there have been notorious problems with
some of the other kinds of build nodes, particularly solaris.

This is just for building the project, not for any kind of deployment.

> 2) , the latest UIMA-AS requires at least JDK 1.6 starting from release
> 2.4.2 due to
> the fact that the ActiveMQ it uses has been compiled with 1.6.

Ok.

> 3) Enabling Findbugs plugin is fine with me.

Ok. Will enable this then.

-- Richard

> Jerry
> 
> 
> 
> 
> 
> On Wed, Dec 4, 2013 at 7:50 AM, Richard Eckart de Castilho
> <re...@apache.org>wrote:
> 
>> Hi,
>> 
>> the UIMA-AS job on Jenkins has the following settings which should
>> probably be updated:
>> 
>> 1) currently bound to "ubuntu1||ubuntu2" -> suggesting "Ubuntu||Windows"
>> 
>> 2) set to use JDK 1.6 (latest) -> suggesting JDK 1.5 (latest)
>> 
>> 3) not running code quality plugins (findbugs, etc.) -> suggesting to
>> enable them
>> 
>> Any objections/comments?
>> 
>> -- Richard


Re: Update Jenkins settings for UIMA-AS?

Posted by Jaroslaw Cwiklik <ui...@gmail.com>.
Hi Richard,

1) Does this setting control what platform the UIMA-AS job is deployed on?

2) , the latest UIMA-AS requires at least JDK 1.6 starting from release
2.4.2 due to
the fact that the ActiveMQ it uses has been compiled with 1.6.

3) Enabling Findbugs plugin is fine with me.

Jerry





On Wed, Dec 4, 2013 at 7:50 AM, Richard Eckart de Castilho
<re...@apache.org>wrote:

> Hi,
>
> the UIMA-AS job on Jenkins has the following settings which should
> probably be updated:
>
> 1) currently bound to "ubuntu1||ubuntu2" -> suggesting "Ubuntu||Windows"
>
> 2) set to use JDK 1.6 (latest) -> suggesting JDK 1.5 (latest)
>
> 3) not running code quality plugins (findbugs, etc.) -> suggesting to
> enable them
>
> Any objections/comments?
>
> -- Richard