Hudson + Jboss AS 7.1 + Maven 3 프로젝트 빌드 오류

Question

프로젝트를 빌드하고 통합 서버에서 테스트를 실행할 수있는 환경을 준비하고 싶습니다. 그래서 Jboss 애플리케이션 서버 7.1을 설치하고 hudson.war을 배포했습니다. 그런 다음 "mvn clean install"을 트리거하는 프로젝트를 만들었습니다. 빌드 할 때 다음 예외가 있습니다.

[INFO] Using bundled Maven 3 installation 
[INFO] Checking Maven 3 installation environment 
[workspace] $ /disk7/hudson_home/maven/slavebundle/bundled-maven/bin/mvn --help 
[INFO] Checking Maven 3 installation version 
[INFO] Detected Maven 3 installation version: 3.0.3 
[workspace] $ /disk7/hudson_home/maven/slavebundle/bundled-maven/bin/mvn clean install -V -B -Dmaven.ext.class.path=/disk7/hudson_home/maven/slavebundle/resources:/disk7/hudson_home/maven/slavebundle/lib/maven3-eventspy-3.0.jar:/disk7/jboss-as-7.1.0.Final/standalone/tmp/vfs/deploymentdf2a6dfa59ee3407/hudson-remoting-2.2.0.jar-407215e5de02980f/contents -Dhudson.eventspy.port=37183 -f pom.xml 
[DEBUG] Waiting for connection on port: 37183 
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200) 
Maven home: /disk7/hudson_home/maven/slavebundle/bundled-maven 
Java version: 1.7.0_04, vendor: Oracle Corporation 
Java home: /usr/lib/jvm/jdk1.7.0_04/jre 
Default locale: en_US, platform encoding: UTF-8 
OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix" 
[ERROR] o.h.m.e.DelegatingEventSpy - Init failed 
java.lang.NoClassDefFoundError: hudson/remoting/Channel 
at org.hudsonci.maven.eventspy.common.RemotingClient.open(RemotingClient.java:103) ~[maven3-eventspy-runtime.jar:na] 
at org.hudsonci.maven.eventspy_30.RemotingEventSpy.openChannel(RemotingEventSpy.java:86) ~[maven3-eventspy-3.0.jar:na] 
at org.hudsonci.maven.eventspy_30.RemotingEventSpy.init(RemotingEventSpy.java:114) ~[maven3-eventspy-3.0.jar:na] 
at org.hudsonci.maven.eventspy_30.DelegatingEventSpy.init(DelegatingEventSpy.java:128) ~[maven3-eventspy-3.0.jar:na] 
at org.apache.maven.eventspy.internal.EventSpyDispatcher.init(EventSpyDispatcher.java:84) [maven-core-3.0.3.jar:3.0.3] 
at org.apache.maven.cli.MavenCli.container(MavenCli.java:403) [maven-embedder-3.0.3.jar:3.0.3] 
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:191) [maven-embedder-3.0.3.jar:3.0.3] 
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) [maven-embedder-3.0.3.jar:3.0.3] 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_04] 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_04] 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_04] 
at java.lang.reflect.Method.invoke(Method.java:601) ~[na:1.7.0_04] 
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) [plexus-classworlds-2.4.jar:na] 
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) [plexus-classworlds-2.4.jar:na] 
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) [plexus-classworlds-2.4.jar:na] 
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) [plexus-classworlds-2.4.jar:na] 
Caused by: java.lang.ClassNotFoundException: hudson.remoting.Channel 
at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) ~[plexus-classworlds-2.4.jar:na] 
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244) ~[plexus-classworlds-2.4.jar:na] 
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230) ~[plexus-classworlds-2.4.jar:na] 
... 16 common frames omitted 
[ERROR] ABORTED 
[ERROR] Failed to initialize 
[ERROR] Caused by: hudson/remoting/Channel 
[ERROR] Caused by: hudson.remoting.Channel 
[ERROR] Failure: java.net.SocketException: Connection reset 
FATAL: Connection reset 
java.net.SocketException: Connection reset 
at java.net.SocketInputStream.read(SocketInputStream.java:189) 
at java.net.SocketInputStream.read(SocketInputStream.java:121) 
at java.io.FilterInputStream.read(FilterInputStream.java:133) 
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) 
at java.io.BufferedInputStream.read(BufferedInputStream.java:254) 
at hudson.remoting.Channel.<init>(Channel.java:385) 
at hudson.remoting.Channel.<init>(Channel.java:347) 
at hudson.remoting.Channel.<init>(Channel.java:320) 
at hudson.remoting.Channel.<init>(Channel.java:315) 
at hudson.slaves.Channels$1.<init>(Channels.java:71) 
at hudson.slaves.Channels.forProcess(Channels.java:71) 
at org.hudsonci.maven.plugin.builder.internal.PerformBuild.doExecute(PerformBuild.java:174) 
at org.hudsonci.utils.tasks.PerformOperation.execute(PerformOperation.java:58) 
at org.hudsonci.maven.plugin.builder.MavenBuilder.perform(MavenBuilder.java:169) 
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:630) 
at hudson.model.Build$RunnerImpl.build(Build.java:175) 
at hudson.model.Build$RunnerImpl.doRun(Build.java:137) 
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:429) 
at hudson.model.Run.run(Run.java:1366) 
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 
at hudson.model.ResourceController.execute(ResourceController.java:88) 
    at hudson.model.Executor.run(Executor.java:145) 

나는 허드슨에 의해 실행하려고하는 명령을 지적 할 :

/disk7로/hudson_home/받는다는/slavebundle/번들-받는다는/빈/MVN 새로 설치 -V -B를 - Dmaven.ext.class.path =/disk7/hudson_home/maven/slavebundle/resources : /disk7/hudson_home/maven/slavebundle/lib/maven3-eventspy-3.0.jar : /disk7/jboss-as-7.1.0. 최종 /standalone/tmp/vfs/deploymentdf2a6dfa59ee3407/hudson-remoting-2.2.0.jar-407215e5de02980f/contents -Dhudson.eventspy.port = 37183 -f 그것은 찾으려고

"허드슨 - 레모의 pom.xml ting-2.2.0.jar "경로를 만들었지 만 엉뚱한 위치에서 검색합니다. hudson-remoting 항아리를 찾았을 때 /disk7/jboss-as-7.1.0.Final/ 이 빌드의 경우 독립 실행 형/tmp/vfs/deploymentdf2a6dfa59ee3407/hudson-remoting-2.2.0.jar-407215e5de02980f/hudson-remoting-2.2.0.jar (내용 없음).

그래서 hudson을 설정하여 강제로 항아리를 찾으십시오. 아이디어가있는 사람이 있습니까?

미리 감사드립니다.

Answer 1

jboss 7을 업그레이드하고 동일한 문제 (jboss 6 hudson에서 잘 작동 함)를 직면합니다. 해결 방법은 적절하지 않지만 잘 작동합니다. 디렉토리 slavebundle/resources에서 hudson-remoting-2.2.0.jar을 추출합니다. jboss 또는 hudson의 새 버전을 기다리고 있습니다.