infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoff Macartney (JIRA)" <>
Subject [jira] [Resolved] (INFRA-13638) "Deploy artifacts to Maven repository" fails when upgrading Jenkins build config to JDK 1.8
Date Thu, 23 Mar 2017 20:04:41 GMT


Geoff Macartney resolved INFRA-13638.
    Resolution: Fixed

Problem must have been a transient thing due to temporary issues on Jenkins around that time.

> "Deploy artifacts to Maven repository" fails when upgrading Jenkins build config to JDK
> -------------------------------------------------------------------------------------------
>                 Key: INFRA-13638
>                 URL:
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Jenkins
>            Reporter: Geoff Macartney
>            Priority: Minor
> I have been trying to update the Apache Brooklyn build jobs to use Java 8
> as a first step towards bringing Brooklyn up from 7 to 8. [1]  I would be grateful for
any help to get this going.
> Most of the builds still worked when I changed the JDK from 1.7 to 1.8. 
> However, the "brooklyn-dist-master" build fails; not when building the code 
> (mvn clean install in the source root), but in one of the Post-build items, 
> namely, the "Deploy artifacts to Maven repository" step.
> When the build runs (in about 20 minutes) with Java 7 [2] this step succeeds and the
logs record first
> numerous archiving steps like
>     [JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/brooklyn-dist-master/pom.xml
to org.apache.brooklyn/brooklyn-dist-root/0.11.0-SNAPSHOT/brooklyn-dist-root-0.11.0-SNAPSHOT.pom
> followed by deploying actions like
>     Deploying the main artifact apache-brooklyn-0.11.0-SNAPSHOT.tar.gz
>     Uploading:
>     Uploaded:
(78847 KB at 3103.4 KB/sec)
> When the build runs with Java 8 this step fails. I have had a simple abort [3], with
output like the
> following (showing the success at the end of the mvn install, followed by "Waiting to
finish collecting
> data" and then eventually an abort):
>     [INFO] ------------------------------------------------------------------------
>     [INFO] ------------------------------------------------------------------------
>     [INFO] Total time: 06:59 min
>     [INFO] Finished at: 2017-03-09T14:42:15+00:00
>     [INFO] Final Memory: 92M/597M
>     [INFO] ------------------------------------------------------------------------
>     Waiting for Jenkins to finish collecting data
>     Build timed out (after 40 minutes). Marking the build as aborted.
>     AbortedBuild was aborted
>     channel stopped
>     Warning: you have no plugins providing access control for builds, so falling back
to legacy behavior of permitting any downstream builds to be triggered
>     Finished: ABORTED
> I also saw [4] it start to do some archiving, and then run into an exception:
>     ERROR: Failed to parse POMs
> Failed to extract /home/jenkins/jenkins-slave/workspace/brooklyn-dist-master/karaf/apache-brooklyn/transfer
of 3 files
>     ...
>     Caused by: This archives contains unclosed entries.
> One difference between [3] and [4] worth mentioning is the build machine.   Our builds
run against
> labels "ubuntu&&!cloud-slave", which maps to machines H14-H18, H21-H24, ubuntu-1
to -6 and some others.
> Of these machines, only H21-H24 have Java 8 on their System Information pages, the rest
have Java 7.
> I'm not sure that this matters, but I mention this in case it does make some difference;
the builds 
> on the other machines seem to have Java 8 anyway, e.g. [4] below ran on H15.
> [1]
> [2]
> [3]
> [4]

This message was sent by Atlassian JIRA

View raw message