CODEWITHSUNDEEP
mavenjenkinsbuild
flash32
flash32

Reputation: 31

Successful Jenkins Build marked as failed

Starting a few days ago, we've had problems with our Jenkins installation that handles the CI and release builds for a medium-sized enterprise project. One particularly annoying issue is the build server marking builds as "failed" (e-mail notification and everything) even though no failure reason at all is apparent from the build log.

Example output for one of our most recent failed builds:

[JENKINS] Recording test results
[INFO] 
[INFO] --- xml-maven-plugin:1.0:validate (default) @ <project name> ---
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] <project name> (application) ................ SUCCESS [  4.408 s]
[INFO] <project name> commons .................. SUCCESS [ 52.580 s]
[INFO] <project name> Database Layer ........... SUCCESS [ 39.305 s]
[INFO] <project name> .......................... SUCCESS [07:57 min]
[INFO] <project name> .............................. SUCCESS [01:51 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13:40 min
[INFO] Finished at: 2015-11-09T15:42:17+01:00
[JENKINS] Archiving disabled
[INFO] Final Memory: 72M/434M
[INFO] ------------------------------------------------------------------------
channel stopped
Finished: SUCCESS

The projects are hosted in an SVN repository and built using maven. Any idea on how I can analyze this issue further?

edit: In response to the question "how do we know it's broken": Jenkins marks the build with a red icon in the overview. We disabled email notification as recommended. unfortunately, this did nothing to change current behavior. Archiving is already disabled. I updated the build output to reflect the current configuration.

Any other ideas?

Upvotes: 2

Views: 6988

Answers (1)

flash32
flash32

Reputation: 31

Managed to fix this myself, by going into the configuration of the failing build jobs, expanding the advanced options of the Maven Jenkins plugin and selecting the option "Run Headless". I do not have the slightest clue as to why this helps, but it does.

Upvotes: 1

Related Questions