Thanks for the update Gav.
I do notice a JAVA_HOME issue on ubuntu-1 with a job that is defined to use JDK: IBM JDK 1.7 64bit (Ubuntu only). Is this included in the scope of your current JDK/Maven/Ant work? I don't see anything open on INFRA JIRA for obviously associated with this. I can report separately for tracking purposes if you wish. https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-IBMJDK1.7/1595/ [Qpid-Java-Java-Test-IBMJDK1.7] $ /home/jenkins/tools/maven/apache-maven-3.0.4/bin/mvn -f ./pom.xml "-Dprofile.specific.excludes=JavaTransientExcludes Java010Excludes IBMJDKExcludes" -Dtest.overridden.properties=./test-profiles/apache-ci.test.overridden.properties clean verify -Pjava-mms.0-10 -fae Error: JAVA_HOME is not defined correctly. We cannot execute /home/jenkins/tools/java/ibm-1.7-64/bin/java Build step 'Invoke top-level Maven targets' marked build as failure On 13 June 2016 at 11:45, Gav <ipv6g...@gmail.com> wrote: > We are busy upgrading slaves and incorporate our puppet configs. > I apologize for any instability over the previous and next few days. > > The JDK/Maven/Ant and other build tools that use 'latest' links will > also get attention. Newer packages will be made available and links > like 'latest' 'latest-$version' will be updated. > > Infra tickets have been filed for some jdk/maven issues so keep an > eye out on those also. > > Thanks > > Gav... > > > On Mon, Jun 13, 2016 at 7:56 PM, Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: >> >> I'd suggest changing the job to use another entry in the version list. >> I thought I had done that already, but obviously not. >> >> The various 'latest' entries for JDK/Maven versions on Jenkins are >> typically out of date (3.0.4 not quite being the most recent Maven, >> for example). Past requests on updating them has been met with 'use >> the explicit versions instead' responses, seemingly due to not wanting >> to update things that might impact existing jobs using them, even >> though many people would likely appreciate it after having perhaps >> picked 'latest' precisely because they thought it might actually be >> recent/updated. It would seem best to remove them entirely in that >> case, but thats also another change to existing jobs. >> >> Robbie >> >> On 13 June 2016 at 10:38, Keith W <keith.w...@gmail.com> wrote: >> > Hi Builds, >> > >> > We are seeing failing on Ubuntu-4 with jobs configured to use "Maven 3 >> > latest". Jenkins is trying to install Maven, but it is consistently >> > failing in the following way. >> > >> > Could someone take a look please? >> > >> > Kind regards, Keith Wall. >> > >> > >> > FATAL: Failed to install >> > >> > https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.0.4/apache-maven-3.0.4-bin.zip >> > to /home/jenkins/tools/maven/apache-maven-3.0.4 >> > java.io.IOException: Failed to install >> > >> > https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.0.4/apache-maven-3.0.4-bin.zip >> > to /home/jenkins/tools/maven/apache-maven-3.0.4 >> > at hudson.FilePath.installIfNecessaryFrom(FilePath.java:832) >> > at >> > hudson.tools.DownloadFromUrlInstaller.performInstallation(DownloadFromUrlInstaller.java:75) >> > at >> > hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68) >> > at >> > hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:108) >> > at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) >> > at hudson.tasks.Maven$MavenInstallation.forNode(Maven.java:624) >> > at hudson.tasks.Maven.perform(Maven.java:288) >> > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) >> > at >> > hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) >> > at hudson.model.Build$BuildExecution.build(Build.java:205) >> > at hudson.model.Build$BuildExecution.doRun(Build.java:162) >> > at >> > hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) >> > at hudson.model.Run.execute(Run.java:1738) >> > at hudson.matrix.MatrixRun.run(MatrixRun.java:146) >> > at hudson.model.ResourceController.execute(ResourceController.java:98) >> > at hudson.model.Executor.run(Executor.java:410) >> > Caused by: java.io.IOException: remote file operation failed: >> > /home/jenkins/tools/maven/apache-maven-3.0.4 at >> > hudson.remoting.Channel@63b327bc:ubuntu-4: >> > java.nio.file.AccessDeniedException: >> > >> > /home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar >> > at hudson.FilePath.act(FilePath.java:986) >> > at hudson.FilePath.act(FilePath.java:968) >> > at hudson.FilePath.deleteContents(FilePath.java:1183) >> > at hudson.FilePath.installIfNecessaryFrom(FilePath.java:796) >> > ... 15 more >> > Caused by: java.nio.file.AccessDeniedException: >> > >> > /home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar >> > at >> > sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) >> > at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) >> > at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) >> > at >> > sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:244) > > > > > -- > Gav...
