[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-09-25 Thread sw...@java.net (JIRA)














































swolk
 commented on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted















After doing some more digging I think I've narrowed down the culprit. This issue was introduced to LTS line after Jenkins ver. 1.532.3. In 1.532.3, the maven plugin user is version 2.0.X. After 1.32.3 when I start seeing the issue, the maven plugin is moved to version 2.1. Between 2.0 and 2.1, the most likely change that caused this regression is https://issues.jenkins-ci.org/browse/JENKINS-19801 (Abort module build when maven build is aborted.)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-09-25 Thread sw...@java.net (JIRA)












































 
swolk
 edited a comment on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted
















After doing some more digging I think I've narrowed down the culprit. This issue was introduced to LTS line after Jenkins ver. 1.532.3. In 1.532.3, the maven plugin user is version 2.0.X. After 1.532.3 when I start seeing the issue, the maven plugin is moved to version 2.1. Between 2.0 and 2.1, the most likely change that caused this regression is https://issues.jenkins-ci.org/browse/JENKINS-19801 (Abort module build when maven build is aborted.)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-09-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted















Would be helpful if we knew in which non LTS version it was introduced if it started between 1.532.3 and 1.554.1...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-09-25 Thread sw...@java.net (JIRA)














































swolk
 commented on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted















The bug was introduced in 1.545. That is the first version that used Maven Project Plugin 2.1. Looking at the code I'm very confident was introduced by changes for https://issues.jenkins-ci.org/browse/JENKINS-19801. That code assumes if modules are still building that main build was aborted, it doesn't take into account the case of parallel module building through -T option and another module failed causing the main build to terminate.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-09-24 Thread sw...@java.net (JIRA)














































swolk
 updated  JENKINS-24832


Failed maven builds using -T are showing up as Aborted
















Change By:


swolk
(24/Sep/14 10:04 PM)




Summary:


Failed
maven
builds
using-T
areshowingupasAborted



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-09-24 Thread dan...@beckweb.net (JIRA)












































 
Daniel Beck
 edited a comment on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted
















(Instructions failed to mention I actually need a goal...)

I get one failed, one successful, and one aborted module, and the overall build status is aborted. Jenkins 1.580(ish), Maven plugin 2.6, building on the CentOS 6 Jenkins master node. So at least it's reproducible.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-09-24 Thread sw...@java.net (JIRA)














































swolk
 updated  JENKINS-24832


Failed maven builds using -T are showing up as Aborted
















Change By:


swolk
(24/Sep/14 10:06 PM)




Attachment:


screenshot-1.jpg



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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


[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2014-09-24 Thread sw...@java.net (JIRA)














































swolk
 commented on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted















Sorry about that. Yep, that is my result as well.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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