AW: Build failed in Jenkins: commons-validator #61

2018-03-14 Thread jhm 
It seems that there is lot of work on the nodes ATM.
So we have to wait for results ...

Jan

> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Mittwoch, 14. März 2018 09:33
> An: 'Commons Developers List'
> Betreff: AW: Build failed in Jenkins: commons-validator #61
> 
> I solved the same problem for commons-email.
> https://builds.apache.org/view/All/job/commons-email/configure
> 
> The project requires via the chosen Maven profile a specific Java
> version.
> This Java installation must be available via a specific environment
> variable "JAVA_1_7_HOME".
> 
> commons-validator sets this to a fixed value, where I don't know this
> location exists on the build node.
> 
> Jenkins could inject the value, but on another name
> "JDK_1_7_LATEST__HOME".
> 'Inject environment variables to the build process > Properties
> Content': "JAVA_1_7_HOME=$JDK_1_7_LATEST__HOME"
> and specify the required value sources via 'Tool Environment'.
> 
> 
> I adapted the email configuration and started a new build.
> 
> 
> Jan
> 
> 
> > -Ursprüngliche Nachricht-
> > Von: sebb [mailto:seb...@gmail.com]
> > Gesendet: Mittwoch, 14. März 2018 00:58
> > An: Commons Developers List
> > Betreff: Re: Build failed in Jenkins: commons-validator #61
> >
> > I think this has happened before.
> >
> > Jenkins now needs Java 8.
> > It attempts recovery but that does not work.
> >
> > On 13 March 2018 at 16:17, Gary Gregory <garydgreg...@gmail.com>
> wrote:
> > > Thoughts on how to fix this?
> > >
> > > Gary
> > >
> > > -- Forwarded message -
> > > From: Apache Jenkins Server <jenk...@builds.apache.org>
> > > Date: Tue, Mar 13, 2018, 09:48
> > > Subject: Build failed in Jenkins: commons-validator #61
> > > To: <notificati...@commons.apache.org>
> > >
> > >
> > > See
> > > <https://builds.apache.org/job/commons-
> validator/61/display/redirect
> > > >
> > >
> > > --
> > > Started by user ggregory
> > > [EnvInject] - Loading node environment variables.
> > > Building remotely on windows-2012-1 (Windows) in workspace <
> > > https://builds.apache.org/job/commons-validator/ws/>
> > > Updating
> > > https://svn.apache.org/repos/asf/commons/proper/validator/trunk at
> > revision '2018-03-13T15:47:38.139 +'
> > > At revision 1826655
> > >
> > > No changes for
> > > https://svn.apache.org/repos/asf/commons/proper/validator/trunk
> > > since the previous build [EnvInject] - Executing scripts and
> > > injecting environment variables after the SCM step.
> > > [EnvInject] - Injecting as environment variables the properties
> > > content JAVA_1_6_HOME=/home/jenkins/tools/java/latest1.6/
> > >
> > > [EnvInject] - Variables injected successfully.
> > > Parsing POMs
> > > Established TCP socket on 62574
> > > maven35-agent.jar already up to date maven35-interceptor.jar
> already
> > > up to date maven3-interceptor-commons.jar already up to date
> > > [commons-validator] $ f:\\jenkins\\tools\\java\\latest1.7/bin/java
> > > -Xmx2g -Xms256m -cp
> > > f:\jenkins\jenkins-slave\maven35-
> > agent.jar;f:\jenkins\tools\maven\late
> > > st3\boot\plexus-classworlds-
> > 2.5.2.jar;f:\\jenkins\\tools\\maven\\lates
> > > t3/conf/logging jenkins.maven3.agent.Maven35Main
> > > f:\\jenkins\\tools\\maven\\latest3
> > > F:\jenkins\jenkins-slave\slave.jar
> > > f:\jenkins\jenkins-slave\maven35-interceptor.jar
> > > f:\jenkins\jenkins-slave\maven3-interceptor-commons.jar 62574
> > > <===[JENKINS REMOTING CAPACITY]===>   channel started
> > > ERROR:
> > >
> >
> ==
> > > ==
> > > ERROR: Invalid project setup:
> jenkins/security/MasterToSlaveCallable
> > :
> > > Unsupported major.minor version 52.0
> > > ERROR: [JENKINS-18403][JENKINS-28294] JDK 'JDK 1.7 (latest)' not
> > > supported to run Maven projects.
> > > ERROR: Maven projects have to be launched with a Java version
> > > greater or equal to the minimum version required by the master.
> > > ERROR: Use the Maven JDK Toolchains (plugin) to build your maven
> > > project with an older JDK.
> > > ERROR: Retrying with slave Java and setting compile/tes

AW: Build failed in Jenkins: commons-validator #61

2018-03-14 Thread jhm 
I solved the same problem for commons-email.
https://builds.apache.org/view/All/job/commons-email/configure

The project requires via the chosen Maven profile a specific Java version.
This Java installation must be available via a specific environment variable 
"JAVA_1_7_HOME".

commons-validator sets this to a fixed value, where I don't know this location 
exists on the build node.

Jenkins could inject the value, but on another name "JDK_1_7_LATEST__HOME".
'Inject environment variables to the build process > Properties Content': 
"JAVA_1_7_HOME=$JDK_1_7_LATEST__HOME"
and specify the required value sources via 'Tool Environment'.


I adapted the email configuration and started a new build.


Jan


> -Ursprüngliche Nachricht-
> Von: sebb [mailto:seb...@gmail.com]
> Gesendet: Mittwoch, 14. März 2018 00:58
> An: Commons Developers List
> Betreff: Re: Build failed in Jenkins: commons-validator #61
> 
> I think this has happened before.
> 
> Jenkins now needs Java 8.
> It attempts recovery but that does not work.
> 
> On 13 March 2018 at 16:17, Gary Gregory  wrote:
> > Thoughts on how to fix this?
> >
> > Gary
> >
> > -- Forwarded message -
> > From: Apache Jenkins Server 
> > Date: Tue, Mar 13, 2018, 09:48
> > Subject: Build failed in Jenkins: commons-validator #61
> > To: 
> >
> >
> > See
> > 
> >
> > --
> > Started by user ggregory
> > [EnvInject] - Loading node environment variables.
> > Building remotely on windows-2012-1 (Windows) in workspace <
> > https://builds.apache.org/job/commons-validator/ws/>
> > Updating
> > https://svn.apache.org/repos/asf/commons/proper/validator/trunk at
> revision '2018-03-13T15:47:38.139 +'
> > At revision 1826655
> >
> > No changes for
> > https://svn.apache.org/repos/asf/commons/proper/validator/trunk since
> > the previous build [EnvInject] - Executing scripts and injecting
> > environment variables after the SCM step.
> > [EnvInject] - Injecting as environment variables the properties
> > content JAVA_1_6_HOME=/home/jenkins/tools/java/latest1.6/
> >
> > [EnvInject] - Variables injected successfully.
> > Parsing POMs
> > Established TCP socket on 62574
> > maven35-agent.jar already up to date
> > maven35-interceptor.jar already up to date
> > maven3-interceptor-commons.jar already up to date [commons-validator]
> > $ f:\\jenkins\\tools\\java\\latest1.7/bin/java -Xmx2g -Xms256m -cp
> > f:\jenkins\jenkins-slave\maven35-
> agent.jar;f:\jenkins\tools\maven\late
> > st3\boot\plexus-classworlds-
> 2.5.2.jar;f:\\jenkins\\tools\\maven\\lates
> > t3/conf/logging jenkins.maven3.agent.Maven35Main
> > f:\\jenkins\\tools\\maven\\latest3
> > F:\jenkins\jenkins-slave\slave.jar
> > f:\jenkins\jenkins-slave\maven35-interceptor.jar
> > f:\jenkins\jenkins-slave\maven3-interceptor-commons.jar 62574
> > <===[JENKINS REMOTING CAPACITY]===>   channel started
> > ERROR:
> >
> ==
> > ==
> > ERROR: Invalid project setup: jenkins/security/MasterToSlaveCallable
> :
> > Unsupported major.minor version 52.0
> > ERROR: [JENKINS-18403][JENKINS-28294] JDK 'JDK 1.7 (latest)' not
> > supported to run Maven projects.
> > ERROR: Maven projects have to be launched with a Java version greater
> > or equal to the minimum version required by the master.
> > ERROR: Use the Maven JDK Toolchains (plugin) to build your maven
> > project with an older JDK.
> > ERROR: Retrying with slave Java and setting compile/test properties
> to
> > point to f:\\jenkins\\tools\\java\\latest1.7.
> > ERROR:
> >
> ==
> > ==
> > Established TCP socket on 62579
> > maven35-agent.jar already up to date
> > maven35-interceptor.jar already up to date
> > maven3-interceptor-commons.jar already up to date [commons-validator]
> > $ "C:\Program Files\Java\jre1.8.0_152/bin/java" -Xmx2g -Xms256m -cp
> > f:\jenkins\jenkins-slave\maven35-
> agent.jar;f:\jenkins\tools\maven\late
> > st3\boot\plexus-classworlds-
> 2.5.2.jar;f:\\jenkins\\tools\\maven\\lates
> > t3/conf/logging jenkins.maven3.agent.Maven35Main
> > f:\\jenkins\\tools\\maven\\latest3
> > F:\jenkins\jenkins-slave\slave.jar
> > f:\jenkins\jenkins-slave\maven35-interceptor.jar
> > f:\jenkins\jenkins-slave\maven3-interceptor-commons.jar 62579
> > <===[JENKINS REMOTING CAPACITY]===>   channel started
> > Executing Maven:  -B -f <
> > https://builds.apache.org/job/commons-validator/ws/pom.xml>
> > -Dmaven.repo.local=f:\jenkins\jenkins-slave\maven-repositories\0 -V
> > clean install --batch-mode -Dgpg.skip -Prelease -Pjava-1.6  [1mApache
> > Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> > 2017-10-18T07:58:13Z) [m
> > Maven home: F:\jenkins\tools\maven\latest3 Java version: 1.8.0_152,
> > vendor: Oracle