Build fails with "UNSTABLE" - but Maven run successfully

[Johannes Schneider]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi guys,

this[1] are the last lines of the console output.
The build is marked as unstable (yellow). I have no idea what might
have gone wrong.

This job used to run just fine. So I don't know what might have changed.
I did an upgraded of jenkins and updated the plugins. So maybe it
might be related to that?

What could I do to get an idea why the build failed?



Thanks,

Johannes




[1] Last lines of the console output:

[INFO]
- ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
- ------------------------------------------------------------------------
[INFO] Total time: 11:52.012s
[INFO] Finished at: Wed Jul 03 22:42:51 CEST 2013
[INFO] Final Memory: 48M/224M
[INFO]
- ------------------------------------------------------------------------
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
Waiting for Jenkins to finish collecting data
channel stopped
Terminating xvnc.
$ /usr/bin/vncserver -kill :66
Killing Xvnc4 process ID 5382
Build did not succeed and the project is configured to only push after
a successful build, so no pushing will occur.
Finished: UNSTABLE
- --

Johannes Schneider - blog.cedarsoft.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJR1JD2AAoJEAytD9R7Qv6dQecH/03TCn29mZd8tDQL4qpjH27q
Umlpf05GBRZ//qSXndlfPGHr4nQ3PVO2YTWzcGN1IkLg2br8HqIwSQ95k8bDxPTh
qAsyM46gSWAVnBLytLoOhCJYGyGGFXrKOUeMBiCWMN6SeARD2t5HX73y6t6UTDdG
GoNBl6T80wEBsg51YhqLUnIhdZiJogbtSl9Tse/M9s/Z580dMvxxXQfKM8cjZn5z
KNE52xDnojqDN9L3l9PQrsTzvy/imwA1GpffzAtwPb5AzUK4FBLfrFtPLwV/OW0O
sktotbxJuD+dAV4QrLB/8p+h8Kvqth+kIQivYFGsgtiJIcP77ftXKWIrPT19Fkc=
=mEo8
-----END PGP SIGNATURE-----

[Tom Fink]

Hi Johannes,

did you solve your issue? I am experiencing the same effect and wandering, what the cause could be...

Cheers

   Tom

[Stephen Connolly]

check for test failures. the evil one[1] tells maven to ignore test failures so that it can parse the test results itself and set the build to unstable instead of failed

[1]: http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4209c619-5ee1-4606-88a9-81a76f869eff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.