incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Svante Schubert <>
Subject Re: Worried about Jenkins..
Date Fri, 24 Feb 2012 00:59:06 GMT
Thank you, Yegor!

The first think I learned was that the builds are called with
    "mvn clean install -Ppedantic"

Never used this parameter before.
The rest was not such new: We are building on JDK 5 with the latest
availabe Maven on the test machines. At least one hour after a code
check-in the build will be triggered, perhaps delayed by other projects.
The build will be aborted if it is stuck more than 120min. Sounds fair.
In addition there is an option of using the Maven FindBugs plugin, what
requires some pom extension
( and PMD analysis, what
we are currently not fully using, but we should IMHO.

As there was long time no build on Windows, I have tested it on Windows
7 and it fails.
[ERROR] Failed to execute goal
org.apache.rat:apache-rat-plugin:0.7:check (default) on project
schema2template: Too many unapproved licenses: 1 -> [Help 1]

Even the -X and -e option did not bring further information. Anyone an
idea? Why should be suddenly a license be missing and why is there no
appropriate error message naming the file?
My final full call was:
    mvn clean install -Ppedantic -X -e -rf :schema2template  >
..\mvn-clean-install--Ppedantic.txt 2>&1
Piping the error and standard output in a test file within a directory
below the subversion.

May I ask all developers of this project to test the latest revision on
their available platforms, with "mvn clean install -Ppedantic"?

PS: I will be soon be off-list till Monday afternoon..


On 23.02.2012 12:04, Yegor Kozlov wrote:
> Svante,
> I granted you access to Jenkins, you should be able to login on
> and configure the project.
> To start with, read the Jenkins Wiki:
> There four types of nodes where Jenkins can run: Ubuntu, Solaris,
> Windows and OSX.
> If you want to build ODFToolkit on multiple or specific nodes then you
> should clone current setup and define ODFToolkit-Windows,
> ODFToolkit-Solaris, etc.
> To tie the project to a specific node you should check "Restrict where
> this project can be run" and set the node label: Ubuntu, Solaris,
> Windows or osx.
> In the current setup this option is unchecked and I guess Jenkins
> selects  the first free node .
> Regards,
> Yegor
> On Wed, Feb 22, 2012 at 8:04 PM, Svante Schubert
> <> wrote:
>> If there are multiple admins, who can have this role, I am fine to assists.
>> What would be your suggestion to fix the problem, Yegor?
>> Svante
>> On 22.02.2012 17:02, Yegor Kozlov wrote:
>>>  I can administer Jenkins and , if you want, I can grant the
>>> hudson-jobadmin role to you.
>>> Yegor
>>> On Wed, Feb 22, 2012 at 5:26 PM, Svante Schubert
>>> <> wrote:
>>>> I am a bit worried about our Jenkins nightly builds, we got one stable
>>>> build out of 19.
>>>> The past builds can be found at
>>>> Build #15 on Ubuntu and #14 on Solaris used a wrong Java (or the build
>>>> was wrong compiled) - see
>>>> Caused by:
>>>> java.lang.UnsupportedClassVersionError: Bad version number in .class file
>>>> and
>>>> Further, I only have seen Ubuntu and Solaris builds and not a single
>>>> Windows build. We need Windows builds as well to detect Window specific
>>>> problems, as path related errors.
>>>> Who is in charge of the Jenkins configuration or could give a helping hand?
>>>> I might need a pointer to a information how to fix Jenkins'
>>>> configuration and if necessary more rights to do so.
>>>> Thanks in advance,
>>>> Svante

View raw message