HELP! Maven builds don't show error messages when run under Jenkins...

3,391 views
Skip to first unread message

Jeff

unread,
Aug 23, 2013, 7:12:00 PM8/23/13
to jenkins...@googlegroups.com
I have a new Jenkins installation (1 master + 1 slave so far).  I have about 8 Maven jobs so far.  When a build fails, the maven errors aren't shown, I only see INFO messages, which seems very odd.  

If I run the maven command on the jenkins system directly, I see the errors.  In the maven options, there is nothing that appears to limit debug output.

I don't know what could cause this and it is driving me mad!!

Any thoughts?  The actual error is an issue resolving a SNAPSHOT dependency that doesn't exist any more.  

Here is the entire output:

Started by user Jeff Vincent
[EnvInject] - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/jobs/fulfillment-lab-service.development/workspace
Checkout:workspace / /var/lib/jenkins/jobs/fulfillment-lab-service.development/workspace - hudson.remoting.LocalChannel@67658c42
Using strategy: Default
Last Built Revision: Revision 657751639cc9a3548bba74f5be3d4844a22cbb0f (origin/development)
Using shallow clone
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Commencing build of Revision 657751639cc9a3548bba74f5be3d4844a22cbb0f (origin/development)
Checking out Revision 657751639cc9a3548bba74f5be3d4844a22cbb0f (origin/development)
Parsing POMs
Modules changed, recalculating dependency graph
[workspace] $ /var/lib/jenkins/tools/hudson.model.JDK/Oracle_JDK_7u25/bin/java -Xmx512m -XX:MaxPermSize=128m -cp /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.4.jar:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_v3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_v3.0.4 /var/cache/jenkins/war/WEB-INF/lib/remoting-2.32.jar /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.4.jar /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar 48830
<===[JENKINS REMOTING CAPACITY]===>channel started
log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
Executing Maven:  -B -f /var/lib/jenkins/jobs/fulfillment-lab-service.development/workspace/pom.xml clean install deploy -U -DskipTests
Aug 23, 2013 4:44:52 PM org.apache.maven.cli.event.ExecutionEventLogger projectDiscoveryStarted
INFO: Scanning for projects...
Aug 23, 2013 4:44:52 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
INFO:                                                                         
Aug 23, 2013 4:44:52 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
INFO: ------------------------------------------------------------------------
Aug 23, 2013 4:44:52 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
INFO: Building fulfillment-lab-service 1.0.0-SNAPSHOT
Aug 23, 2013 4:44:52 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
INFO: ------------------------------------------------------------------------
[WARNING] The POM for com.mycompany.serviceclients:xapi-service:jar:1.4.1-20130823.222403-1 is missing, no dependency information available
Aug 23, 2013 4:44:55 PM org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: ------------------------------------------------------------------------
Aug 23, 2013 4:44:55 PM org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: BUILD FAILURE
Aug 23, 2013 4:44:55 PM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: ------------------------------------------------------------------------
Aug 23, 2013 4:44:55 PM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Total time: 3.386s
Aug 23, 2013 4:44:55 PM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Finished at: Fri Aug 23 16:44:55 MDT 2013
Aug 23, 2013 4:44:55 PM org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Final Memory: 9M/121M
Aug 23, 2013 4:44:55 PM org.apache.maven.cli.event.ExecutionEventLogger sessionEnded
INFO: ------------------------------------------------------------------------
[JENKINS] Archiving /var/lib/jenkins/jobs/fulfillment-lab-service.development/workspace/pom.xml to /var/lib/jenkins/jobs/fulfillment-lab-service.development/modules/com.mycompany.fulfillment$fulfillment-lab-service/builds/2013-08-23_16-44-48/archive/com.mycompany.fulfillment/fulfillment-lab-service/1.0.0-SNAPSHOT/fulfillment-lab-service-1.0.0-SNAPSHOT.pom
Waiting for Jenkins to finish collecting data
channel stopped
Skipping sonar analysis due to bad build status FAILURE
Sending e-mails to: fulfill...@mycompany.com
Finished: FAILURE


--
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

Vincent Latombe

unread,
Aug 24, 2013, 2:55:34 AM8/24/13
to Jenkins Users
Hi Jeff,

it's a bug introduced in core/maven-plugin a few versions ago. I think I saw a commit fixing it this week so it will released either with 1.530 or 1.531.

If you are starting with Jenkins, I can only recommend you to install the LTS version rather than the latest version. This will avoid most problems like this.

Cheers,

Vincent

Vincent


2013/8/24 Jeff <preda...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Baptiste Mathus

unread,
Aug 24, 2013, 8:06:13 AM8/24/13
to jenkins...@googlegroups.com

Unrelated, but having "clean install deploy" as goals is wasteful.

You should do only "clean deploy" as deploy actually includes the 'install' part.

Cheers

Jeff

unread,
Aug 24, 2013, 10:42:13 PM8/24/13
to jenkins...@googlegroups.com
Thanks for the feedback...and yeah, the "clean install deploy" is redundant for the "install" part, but in most cases install is often the end goal and I type it out of habit.

As long as I know it's getting worked on, I'm happy to continue on.

Felix Riegger

unread,
Sep 23, 2013, 3:03:36 AM9/23/13
to jenkins...@googlegroups.com
Hi Vincent,

we are on 1.531 now, but the problem is still present. Is there a ticket to this problem?

Kind regards,
Felix

Vincent Latombe

unread,
Sep 23, 2013, 3:17:55 AM9/23/13
to Jenkins Users

Vincent


2013/9/23 Felix Riegger <felix....@gmail.com>

Clint Bodine

unread,
Nov 7, 2013, 12:02:45 AM11/7/13
to jenkins...@googlegroups.com
FWIW, we recently upgraded to Jenkins 1.534 and just ran into this problem.

Stephen Connolly

unread,
Nov 7, 2013, 5:40:11 AM11/7/13
to jenkins...@googlegroups.com


--

Vineet Yadav

unread,
Sep 5, 2016, 2:30:35 AM9/5/16
to Jenkins Users
please provide permission on your project .

Karl Heinz Marbaise

unread,
Sep 5, 2016, 2:35:33 AM9/5/16
to jenkins...@googlegroups.com
Hi,


The basic problem with you build what i can identify from the output is:

[WARNING] The POM for
com.mycompany.serviceclients:xapi-service:jar:1.4.1-20130823.222403-1 is
missing, no dependency information available

THis means your configuration for proxy/repository manager etc. seemed
to be wrong or simply the above SNAPSHOT has been removed cause that is
referencing an very old SNAPSHOT which are usually removed and should
never referenced in projects...


Kind regards
Karl Heinz Marbaise
> Executing Maven: * -B -f
> /var/lib/jenkins/jobs/fulfillment-lab-service.development/workspace/pom.xml
> clean install deploy -U -DskipTests*
> Sending e-mails to: fulfill...@mycompany.com <javascript:>
> Finished: FAILURE
>
>
>
Reply all
Reply to author
Forward
0 new messages