infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-13810) Jenkins suddenly pointing to Maven 3 latest
Date Wed, 12 Apr 2017 11:46:41 GMT

     [ https://issues.apache.org/jira/browse/INFRA-13810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin updated INFRA-13810:
--------------------------
    Status: Waiting for user  (was: Waiting for Infra)

We do not point jobs to Maven (latest) or any other latest, we try and leave job configs to
projects. However, recent plugin upgrades especially with regard to Maven job types and Java
may have had people try alternate settings.

Those projects choosing 'latest' links can expect to have their versions change without notice.
(So some like yourselves choose to stick to a specific version until ready to change.)

I'm not sure what else to tell you here, do you want more investigation, or is making us aware
enough for now?

> Jenkins suddenly pointing to Maven 3 latest
> -------------------------------------------
>
>                 Key: INFRA-13810
>                 URL: https://issues.apache.org/jira/browse/INFRA-13810
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: John D. Ament
>            Assignee: Gavin
>
> A number of our Jenkins jobs were pointing to older Maven 3 releases.  The main reason
begin that Maven requires certain JVM levels to operate, we need to test our code not only
that it compiles to a certain language level but that it operates on that language level.
 A number of our jobs were using combinations of 1.6 and older Maven to ensure that the maven
runtime we used operated on that Java version.  Starting this past weekend, a number of our
jobs started to fail.  These jobs all failed with similar errors:
> [DeltaSpike_AS7] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g -Xms256m -cp /home/jenkins/jenkins-slave/maven33-agent.jar:/home/jenkins/tools/maven/latest3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest3/conf/logging
jenkins.maven3.agent.Maven33Main /home/jenkins/tools/maven/latest3/ /home/jenkins/jenkins-slave/slave.jar
/home/jenkins/jenkins-slave/maven33-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar
39153
> Native maven support requires Java 1.7 or later, but this Maven is using /usr/local/asfpackages/java/jdk1.6.0_45-64/jre
> If I look at this job in particular: https://builds.apache.org/job/DeltaSpike_AS7/ ,
I can see that it was pointing to Maven 3 (latest) when it used to point to something else
(I'm not sure what that something else was TBH).  I've repointed this job in particular to
3.0.5.
> I'm not 100% sure what this error means, if its related to recent changes or what.  I
see no audit trail indicating a job configuration change.  If we need to reconfigure our jobs
to point back to Maven 3.0.5, that's fine, but was this intentional? Or is something else
broken?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message