-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins 1.565.2
After upgrading to Jenkins 1.565.2, I'm seeing some builds showing up with status Aborted instead of Failed when there is a compilation issue. We use maven jobs and have incremental building enabled (this has worked fine for us for a long time.) We also use multiple threads for the maven build. Seems if one thread is in the middle of running unit tests where as the other one compiles and fails, then the other thread gets killed and status for module shows as ABORTED in main server log. Could this be caused by https://issues.jenkins-ci.org/browse/JENKINS-22641 fix introduced in latest LTS release?
[woot@eng301 logs]$ grep 13179 catalina.out | grep apps-nonstop INFO: SCM changes detected in apps-nonstop. Triggering #13179 INFO: apps-nonstop/com.netbase:deploy #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-prospero-widget #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-stream-server #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:prospero-framework #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:transformer #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-cb-closure #13179 main build action completed: ABORTED INFO: apps-nonstop/com.netbase:dailyupdate #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:persist-api #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:alert-manager #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:content-api #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-iodocs #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:persist-cb #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:log #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:rosalind #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:acc-block-result #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:content-rosalind #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-ariel #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:consumerbase2 #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-ix #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:nlp #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:test #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:cb-insight-api-tools #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:app-cb #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:prospero-api #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:prospero-lucene4 #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:applications #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:megatron #13179 main build action completed: NOT_BUILT INFO: apps-nonstop/com.netbase:engine-lucene4 #13179 main build action completed: NOT_BUILT INFO: apps-nonstop #13179 main build action completed: FAILURE
- is related to
-
-
- Resolved
-
- links to
[JENKINS-24832] Failed maven builds using -T are showing up as Aborted
Michael Sawyer
added a comment - We have been using our build of this plugin since June with no real issues. Sometimes a module will continue running after the build is Failed/Aborted, but it does eventually die.
Michael Sawyer
added a comment - We have been using our build of this plugin since June with no real issues. Sometimes a module will continue running after the build is Failed/Aborted, but it does eventually die. The PR has some comments which have not been responded to since June. There is no real plugin owner; always safer to use a freestyle project.
Michael Sawyer
added a comment - Sorry, to clarify I have been using the version of the plugin found in the PR. I didn't notice a question asked on there though, so I didn't respond. I did notice you mentioned it is a slight improvement over what is currently out there, and again we haven't had any issues using it, so I would recommend pulling it in.
P.S., It was cool seeing you at JUC jglick
Michael Sawyer
added a comment - Sorry, to clarify I have been using the version of the plugin found in the PR. I didn't notice a question asked on there though, so I didn't respond. I did notice you mentioned it is a slight improvement over what is currently out there, and again we haven't had any issues using it, so I would recommend pulling it in.
P.S., It was cool seeing you at JUC jglick Experiencing the same issue with Jenkins 1.627, Maven plugin 2.12.1
It is critical because developers are not notified when builds are aborted (usually manual action)
If there is a fix, why is it still not merged?
As a workaround, until this is fixed, you can use a groovy post-build script that changes the status of the build from ABORTED to FAILED in case it finds the error in the log.
See a post I've wrote about it: http://www.tikalk.com/devops/JenkinsJobStatusChange
I just created a new PR ( https://github.com/jenkinsci/maven-plugin/pull/79 ) which is taking care of jglick comments. I hope to merge it in the next release if the review is ok
Code changed in jenkins
User: Arnaud Heritier
Path:
src/main/java/hudson/maven/MavenModuleSetBuild.java
src/test/java/hudson/maven/MavenMultiModuleTest.java
src/test/resources/hudson/maven/maven-multimod-failure.zip
http://jenkins-ci.org/commit/maven-plugin/2e671da7a66fc24530d82daef5c7d226414e7978
Log:
Fixes JENKINS-24832 : Failed maven builds using -T are showing up as Aborted (#79)
Why is the fix not merged? We suffer from this too.