|
|
|
|
Change By:
|
Holger Lehmann
(18/Nov/13 5:10 PM)
|
Summary:
|
The
current
version
0.27
of
Jenkins
the ArtifactDeployer Plugin
breaks all Maven 2 jobs
|
Description:
|
The current version of Jenkins is only capable of running Maven 3 Tasks
when the ArtifactDeployer plugin is installed
. Any Maven 2 I tried fails with the java exception from below. This breaks *all* of our jobs since we develop Atlassian JIRA/Confluence plugins and thus need Atlassians Maven 2 (or equivalent).
Googling did not produce anything suitable :-(
I will attach any logfiles if required, please let me know.
This failure occurred *after* upgrading to the latest version from (I think) 1.531 (RPM)
Jenkins is running as user "jenkins"
This is the Java stacktrace: --- {noformat} java.io.IOException: Remote call on Channel to Maven [java, -Djava.awt.headless=true, -cp, /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.4.jar:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Default_Maven_2/boot/classworlds-1.1.jar, hudson.maven.agent.Main, /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Default_Maven_2, /tmp/jetty-0.0.0.0-9080-jenkins.war-_jenkins-any-/webapp/WEB-INF/lib/remoting-2.32.jar, /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.4.jar, 58820, /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar] failed at hudson.remoting.Channel.call(Channel.java:723) at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:160) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:823) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1679) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of org/codehaus/classworlds/RealmClassLoader) previously initiated loading for a different type with name "org/codehaus/plexus/configuration/PlexusConfiguration" 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 org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getMethod0(Class.java:2679) at java.lang.Class.getMethod(Class.java:1605) at hudson.maven.MavenBuilder.callSetListenerWithReflectOnInterceptors(MavenBuilder.java:211) at hudson.maven.MavenBuilder.callSetListenerWithReflectOnInterceptorsQuietly(MavenBuilder.java:231) at hudson.maven.MavenBuilder.call(MavenBuilder.java:199) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) {noformat}
|
Component/s:
|
artifactdeployer
|
Component/s:
|
artifactory
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
Disabling ArtifactDeployer (Artifactory) for the builds is a workaround to get, at least, Jenkins up and running again.
I will evaluate the 0.28 version today.