I have previously emailed about this on the main clerezza build, but I have absolutely nothing to do with this project and am still regularly getting spammed with build failures. The issue previously was that you had a flag for "Send separate emails to individuals who broke the build" ticked on the main Clerezza build. I continue to get emails for clerezza-site, but please audit all your Jenkins jobs and remove this option; it is clearly misidentifying emails and spamming them with build failure noise.
On Thu, Feb 20, 2020, at 4:07 PM, Apache Jenkins Server wrote: > See > <https://builds.apache.org/job/clerezza-site/621/display/redirect?page=changes> > > Changes: > > [Hasan] CLEREZZA-1057: Add releases/20200220 > > [Hasan] [maven-release-plugin] prepare release partial-release-20200220-3 > > [Hasan] [maven-release-plugin] prepare for next development iteration > > > ------------------------------------------ > Started by an SCM change > Running as SYSTEM > [EnvInject] - Loading node environment variables. > Building remotely on H44 (ubuntu) in workspace > <https://builds.apache.org/job/clerezza-site/ws/> > No credentials specified > > git rev-parse --is-inside-work-tree # timeout=10 > Fetching changes from the remote Git repository > > git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/clerezza.git # timeout=10 > Fetching upstream changes from > https://git-wip-us.apache.org/repos/asf/clerezza.git > > git --version # timeout=10 > > git fetch --tags --progress -- > https://git-wip-us.apache.org/repos/asf/clerezza.git > +refs/heads/*:refs/remotes/origin/* > > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 > Checking out Revision 67d2d055847d4ec1c58437516605a27e37d75119 > (refs/remotes/origin/master) > > git config core.sparsecheckout # timeout=10 > > git checkout -f 67d2d055847d4ec1c58437516605a27e37d75119 > Commit message: "[maven-release-plugin] prepare for next development > iteration" > > git rev-list --no-walk 53b582d31386ed31e3dde3282cc05973e7d6a65e # > timeout=10 > [locks-and-latches] Checking to see if we really have the locks > [locks-and-latches] Have all the locks, build can start > Parsing POMs > Established TCP socket on 43797 > maven3-agent.jar already up to date > maven3-interceptor.jar already up to date > maven3-interceptor-commons.jar already up to date > [parent] $ /home/jenkins/tools/java/latest1.6/bin/java > -XX:MaxPermSize=256m -cp > /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar > org.jvnet.hudson.maven3.agent.Maven3Main > /home/jenkins/tools/maven/apache-maven-3.0.5 > /home/jenkins/jenkins-slave/remoting.jar > /home/jenkins/jenkins-slave/maven3-interceptor.jar > /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 43797 > Exception in thread "main" java.lang.UnsupportedClassVersionError: > org/jvnet/hudson/maven3/agent/Maven3Main : Unsupported major.minor > version 52.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) > at java.lang.ClassLoader.defineClass(ClassLoader.java:615) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) > at java.net.URLClassLoader.access$000(URLClassLoader.java:58) > at java.net.URLClassLoader$1.run(URLClassLoader.java:197) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > Could not find the main class: > org.jvnet.hudson.maven3.agent.Maven3Main. Program will exit. > [locks-and-latches] Releasing all the locks > [locks-and-latches] All the locks released > ERROR: Failed to launch Maven. Exit code = 1 >
