Build Maven submodule => ABORTED
Locked
Build Maven submodule => ABORTED
 
|
Hi, I am running Jenkins 1.440. I have a Maven Job that is a multi-module project (aggregator pom and several submodules). When I try to run the build for a given submodule only (going on the job page -> Modules -> "Build" on the given submodule) it is not working. In the console I get: Démarré par l'utilisateur "me" Reporters=[hudson.maven.reporters.MavenArtifactArchiver@d96f4a, hudson.maven.reporters.MavenFingerprinter@1199a13, hudson.maven.reporters.BuildInfoRecorder@1d28b4d, hudson.maven.reporters.MavenSiteArchiver@1b77458, hudson.maven.reporters.MavenJavadocArchiver@1376230, hudson.maven.reporters.SurefireArchiver@10f6d1f, hudson.maven.reporters.MavenTestJavadocArchiver@1c53efa] Starting xvnc [xxx-parent] $ vncserver :49 New 'xxx:49 (jenkins)' desktop is xxx:49 Starting applications specified in /home/jenkins/.vnc/xstartup Log file is /home/jenkins/.vnc/xxx:49.log $ /home/jenkins/data/tools/JDK_6/bin/java -Xmx512m -XX:MaxPermSize=256m -cp /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/jenkins/apache-maven-3.0.3/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/apache-maven-3.0.3 /home/jenkins/data/war/WEB-INF/lib/remoting-2.11.jar /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 59549 <===[JENKINS REMOTING CAPACITY]===>channel started Finished: ABORTED Doing the same on our "old" Jenkins 1.399 instance is working fine: Démarré par l'utilisateur "me" Starting xvnc [xxx-parent] $ vncserver :14 New 'xxx:14 (jenkins)' desktop is xxx:14 Starting applications specified in /home/jenkins/.vnc/xstartup Log file is /home/jenkins/.vnc/xxx:14.log Found mavenVersion 2.2.1 from file jar:file:/home/jenkins/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties $ java -Xmx512m -XX:MaxPermSize=256m -cp /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.399.jar:/home/jenkins/apache-maven-2.2.1/boot/classworlds-1.1.jar hudson.maven.agent.Main /home/jenkins/apache-maven-2.2.1 /home/jenkins/data/war/WEB-INF/lib/remoting-1.399.jar /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.399.jar 58514 /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar <===[HUDSON REMOTING CAPACITY]===>channel started Executing Maven: -N -B -f /home/jenkins/data/jobs/H00078_L12_DEV/workspace/H00078_L12_DEV/macif-parent/pom.xml --batch-mode --errors clean deploy [...] Finished:
SUCCESS Do you have some clue to understand why the build is aborted? Thanks Julien |
Re: Build Maven submodule => ABORTED
|
|
Any other differences e.g. switching from Maven 2.x to 3.x for building the project?
Building single modules with Maven 3 is not implemented, yet, and marks the builds simply as aborted. -------- Original-Nachricht -------- > Datum: Thu, 1 Dec 2011 12:26:13 +0000 (GMT) > Von: Julien HENRY <[hidden email]> > An: "[hidden email]" <[hidden email]> > Betreff: Build Maven submodule => ABORTED > Hi, > > I am running Jenkins 1.440. I have a Maven Job that is a multi-module > project (aggregator pom and several submodules). > When I try to run the build for a given submodule only (going on the job > page -> Modules -> "Build" on the given submodule) it is not working. In the > console I get: > > Démarré par l'utilisateur "me" > Reporters=[hudson.maven.reporters.MavenArtifactArchiver@d96f4a, > hudson.maven.reporters.MavenFingerprinter@1199a13, > hudson.maven.reporters.BuildInfoRecorder@1d28b4d, hudson.maven.reporters.MavenSiteArchiver@1b77458, > hudson.maven.reporters.MavenJavadocArchiver@1376230, > hudson.maven.reporters.SurefireArchiver@10f6d1f, hudson.maven.reporters.MavenTestJavadocArchiver@1c53efa] > Starting xvnc > [xxx-parent] $ vncserver :49 > > New 'xxx:49 (jenkins)' desktop is xxx:49 > > Starting applications specified in /home/jenkins/.vnc/xstartup > Log file is /home/jenkins/.vnc/xxx:49.log > > $ /home/jenkins/data/tools/JDK_6/bin/java -Xmx512m -XX:MaxPermSize=256m > -cp > /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/jenkins/apache-maven-3.0.3/boot/plexus-classworlds-2.4.jar > org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/apache-maven-3.0.3 > /home/jenkins/data/war/WEB-INF/lib/remoting-2.11.jar > /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 59549 > <===[JENKINS REMOTING CAPACITY]===>channel started > Finished: ABORTED > > Doing the same on our "old" Jenkins 1.399 instance is working fine: > > Démarré par l'utilisateur "me" > Starting xvnc > [xxx-parent] $ vncserver :14 > > New 'xxx:14 (jenkins)' desktop is xxx:14 > > Starting applications specified in /home/jenkins/.vnc/xstartup > Log file is /home/jenkins/.vnc/xxx:14.log > > Found mavenVersion 2.2.1 from file > jar:file:/home/jenkins/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties > $ java -Xmx512m -XX:MaxPermSize=256m -cp > /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.399.jar:/home/jenkins/apache-maven-2.2.1/boot/classworlds-1.1.jar > hudson.maven.agent.Main /home/jenkins/apache-maven-2.2.1 > /home/jenkins/data/war/WEB-INF/lib/remoting-1.399.jar > /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.399.jar 58514 > /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar > <===[HUDSON REMOTING CAPACITY]===>channel started > Executing Maven: -N -B -f > /home/jenkins/data/jobs/H00078_L12_DEV/workspace/H00078_L12_DEV/macif-parent/pom.xml --batch-mode --errors clean deploy > [...] > Finished: SUCCESS > > Do you have some clue to understand why the build is aborted? > > Thanks > > Julien |
Re: Build Maven submodule => ABORTED
|
|
Good catch! We have switched to Maven 3.
Is there any plan to reintroduce this feature with Maven3? Is there any JIRA issue I can follow? Waiting for the fix, maybe the build button could be hidden on submodules to not expose a feature that is not working? Thanks, Julien >________________________________ > De : Christoph Kutzinski <[hidden email]> >À : [hidden email] >Envoyé le : Jeudi 1 Décembre 2011 13h56 >Objet : Re: Build Maven submodule => ABORTED > >Any other differences e.g. switching from Maven 2.x to 3.x for building the project? >Building single modules with Maven 3 is not implemented, yet, and marks the builds simply as aborted. > > > > >-------- Original-Nachricht -------- >> Datum: Thu, 1 Dec 2011 12:26:13 +0000 (GMT) >> Von: Julien HENRY <[hidden email]> >> An: "[hidden email]" <[hidden email]> >> Betreff: Build Maven submodule => ABORTED > >> Hi, >> >> I am running Jenkins 1.440. I have a Maven Job that is a multi-module >> project (aggregator pom and several submodules). >> When I try to run the build for a given submodule only (going on the job >> page -> Modules -> "Build" on the given submodule) it is not working. In the >> console I get: >> >> Démarré par l'utilisateur "me" >> Reporters=[hudson.maven.reporters.MavenArtifactArchiver@d96f4a, >> hudson.maven.reporters.MavenFingerprinter@1199a13, >> hudson.maven.reporters.BuildInfoRecorder@1d28b4d, hudson.maven.reporters.MavenSiteArchiver@1b77458, >> hudson.maven.reporters.MavenJavadocArchiver@1376230, >> hudson.maven.reporters.SurefireArchiver@10f6d1f, hudson.maven.reporters.MavenTestJavadocArchiver@1c53efa] >> Starting xvnc >> [xxx-parent] $ vncserver :49 >> >> New 'xxx:49 (jenkins)' desktop is xxx:49 >> >> Starting applications specified in /home/jenkins/.vnc/xstartup >> Log file is /home/jenkins/.vnc/xxx:49.log >> >> $ /home/jenkins/data/tools/JDK_6/bin/java -Xmx512m -XX:MaxPermSize=256m >> -cp >> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/jenkins/apache-maven-3.0.3/boot/plexus-classworlds-2.4.jar >> org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/apache-maven-3.0.3 >> /home/jenkins/data/war/WEB-INF/lib/remoting-2.11.jar >> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 59549 >> <===[JENKINS REMOTING CAPACITY]===>channel started >> Finished: ABORTED >> >> Doing the same on our "old" Jenkins 1.399 instance is working fine: >> >> Démarré par l'utilisateur "me" >> Starting xvnc >> [xxx-parent] $ vncserver :14 >> >> New 'xxx:14 (jenkins)' desktop is xxx:14 >> >> Starting applications specified in /home/jenkins/.vnc/xstartup >> Log file is /home/jenkins/.vnc/xxx:14.log >> >> Found mavenVersion 2.2.1 from file >> jar:file:/home/jenkins/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties >> $ java -Xmx512m -XX:MaxPermSize=256m -cp >> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.399.jar:/home/jenkins/apache-maven-2.2.1/boot/classworlds-1.1.jar >> hudson.maven.agent.Main /home/jenkins/apache-maven-2.2.1 >> /home/jenkins/data/war/WEB-INF/lib/remoting-1.399.jar >> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.399.jar 58514 >> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar >> <===[HUDSON REMOTING CAPACITY]===>channel started >> Executing Maven: -N -B -f >> /home/jenkins/data/jobs/H00078_L12_DEV/workspace/H00078_L12_DEV/macif-parent/pom.xml --batch-mode --errors clean deploy >> [...] >> Finished: SUCCESS >> >> Do you have some clue to understand why the build is aborted? >> >> Thanks >> >> Julien > > > |
Re: Build Maven submodule => ABORTED
|
|
AFAIK there's no Jira issue for that one, yet. Feel free to create one.
-- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. Julien HENRY <[hidden email]> schrieb: Good catch! We have switched to Maven 3. |
Re: Build Maven submodule => ABORTED
|
|
Done: https://issues.jenkins-ci.org/browse/JENKINS-11964
>________________________________ > De : Christoph Kutzinski <[hidden email]> >À : [hidden email] >Envoyé le : Jeudi 1 Décembre 2011 18h57 >Objet : Re: Build Maven submodule => ABORTED > > >AFAIK there's no Jira issue for that one, yet. Feel free to create one. >-- >Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. > > > > >Julien HENRY <[hidden email]> schrieb: >Good catch! We have switched to Maven 3. >> >>Is there any plan to reintroduce this feature with Maven3? Is there any JIRA issue I can follow? Waiting for the fix, maybe the build button could be hidden on submodules to not expose a feature that is not working? >> >> >>Thanks, >> >>Julien >> >>> >>________________________________ >> >>> De : Christoph Kutzinski <[hidden email]> >>>À : [hidden email] >>>Envoyé le : Jeudi 1 Décembre 2011 13h56 >>>Objet : Re: Build Maven submodule => ABORTED >>> >>>Any other differences e.g. switching from Maven 2.x to 3.x for building the project? >>>Building single modules with Maven 3 is not implemented, yet, and marks the builds simply as aborted. >>> >>> >>> >>> >>>-------- Original-Nachricht -------- >>>> Datum: Thu, 1 Dec 2011 12:26:13 +0000 (GMT) >>>> Von: Julien HENRY <[hidden email]> >>>> An: "[hidden email]" <[hidden email]> >>>> Betreff: Build Maven submodule => ABORTED >>> >>>> Hi, >>>> >>>> I am running Jenkins 1.440. I have a Maven Job that is a multi-module >>>> project (aggregator pom and several submodules). >>>> When I try to run the build for a given submodule only (going on the job >>>> page -> Modules -> "Build" on the given submodule) it is not working. In the >>>> console I get: >>>> >>>> Démarré par l'utilisateur "me" >>>> Reporters=[hudson.maven.reporters.MavenArtifactArchiver@d96f4a, >>>> hudson.maven.reporters.MavenFingerprinter@1199a13, >>>> hudson.maven.reporters.BuildInfoRecorder@1d28b4d, hudson.maven.reporters.MavenSiteArchiver@1b77458, >>>> >>>> hudson.maven.reporters.SurefireArchiver@10f6d1f, hudson.maven.reporters.MavenTestJavadocArchiver@1c53efa] >>>> Starting xvnc >>>> [xxx-parent] $ vncserver :49 >>>> >>>> New 'xxx:49 (jenkins)' desktop is xxx:49 >>>> >>>> Starting applications specified in /home/jenkins/.vnc/xstartup >>>> Log file is /home/jenkins/.vnc/xxx:49.log >>>> >>>> $ /home/jenkins/data/tools/JDK_6/bin/java -Xmx512m -XX:MaxPermSize=256m >>>> -cp >>>> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/jenkins/apache-maven-3.0.3/boot/plexus-classworlds-2.4.jar >>>> org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/apache-maven-3.0.3 >>>> /home/jenkins/data/war/WEB-INF/lib/remoting-2.11.jar >>>> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 59549 >>>> <===[JENKINS REMOTING CAPACITY]===>channel started >>>> Finished: ABORTED >>>> >>>> Doing the same on our "old" Jenkins 1.399 instance is working fine: >>>> >>>> Démarré par l'utilisateur "me" >>>> Starting xvnc >>>> [xxx-parent] $ vncserver :14 >>>> >>>> New 'xxx:14 (jenkins)' desktop is xxx:14 >>>> >>>> Starting applications specified in /home/jenkins/.vnc/xstartup >>>> Log file is /home/jenkins/.vnc/xxx:14.log >>>> >>>> Found mavenVersion 2.2.1 from file >>>> jar:file:/home/jenkins/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties >>>> $ java -Xmx512m -XX:MaxPermSize=256m -cp >>>> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.399.jar:/home/jenkins/apache-maven-2.2.1/boot/classworlds-1.1.jar >>>> hudson.maven.agent.Main >>>> /home/jenkins/data/war/WEB-INF/lib/remoting-1.399.jar >>>> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.399.jar 58514 >>>> /home/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar >>>> <===[HUDSON REMOTING CAPACITY]===>channel started >>>> Executing Maven: -N -B -f >>>> /home/jenkins/data/jobs/H00078_L12_DEV/workspace/H00078_L12_DEV/macif-parent/pom.xml --batch-mode --errors clean deploy >>>> [...] >>>> Finished: SUCCESS >>>> >>>> Do you have some clue to understand why the build is aborted? >>>> >>>> Thanks >>>> >>>> Julien >>> >>> >>> >> > > |
«
Return to Jenkins users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |