[JIRA] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9

2014-09-16 Thread bren...@letrabb.com (JIRA)














































Brantone
 commented on  JENKINS-21615


MultiJob 1.11 phases broken when upgraded from 1.9















Update? 7 months on a blocker 



























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] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9

2014-09-16 Thread yora...@tikalk.com (JIRA)












































 
Yoram Michaeli
 edited a comment on  JENKINS-21615


MultiJob 1.11 phases broken when upgraded from 1.9
















Can you send some details about your multi-job and the jobs which you activates in the phases?
Also, can you send the console output of the multijob session?
I've tried to reproduce the bug (the first reported with the 2 phases) and all looks as working OK.



























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] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9

2014-09-16 Thread yora...@tikalk.com (JIRA)














































Yoram Michaeli
 commented on  JENKINS-21615


MultiJob 1.11 phases broken when upgraded from 1.9















@imakowski, can you send some details about your multi-job and the jobs which you activates in the phases?
Also, can you send the console output of the multijob session?
I've tried to reproduce the bug (the first reported with the 2 phases) and all looks as working OK.



























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] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9

2014-02-04 Thread nmo...@kalray.eu (JIRA)














































Nicolas Morey
 commented on  JENKINS-21615


MultiJob 1.11 phases broken when upgraded from 1.9















I updated from 1.4 to 1.11 and had the same kind of issue.
The job in the phase are matrix build. I tried a small test case and I get this backtrace:
java.lang.ClassCastException: hudson.matrix.MatrixBuild cannot be cast to hudson.model.Build
	at com.tikal.jenkins.plugins.multijob.MultiJobBuilder$SubJobWorker.run(MultiJobBuilder.java:199)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:722)



























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/groups/opt_out.


[JIRA] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9

2014-02-02 Thread imakow...@gmail.com (JIRA)














































Ireneusz Makowski
 created  JENKINS-21615


MultiJob 1.11 phases broken when upgraded from 1.9















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


jenkins-multijob-plugin



Created:


02/Feb/14 3:20 PM



Description:


When there were 2 phases in multijob with only one job executed per phase then all the jobs are executed at once, and phases are ignored!

The second braking change is failure of entire phase and multijob when one of the jobs fails during build! Upgrade should change this value to Never not Failure, because it changes flows after upgrade to 1.11. 




Environment:


Windows 2008 R2 64 bit, Jenkins 1.532.1 LTS




Fix Versions:


current



Project:


Jenkins



Labels:


plugin
jenkins
lts
lts-candidate




Priority:


Blocker



Reporter:


Ireneusz Makowski

























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/groups/opt_out.


[JIRA] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9

2014-02-02 Thread hag...@java.net (JIRA)














































hagzag
 commented on  JENKINS-21615


MultiJob 1.11 phases broken when upgraded from 1.9















Checking the issue - AFAIK it shouldn't, I will update ASAP



























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/groups/opt_out.


[JIRA] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9

2014-02-02 Thread imakow...@gmail.com (JIRA)














































Ireneusz Makowski
 commented on  JENKINS-21615


MultiJob 1.11 phases broken when upgraded from 1.9















Great. Waiting for info.



























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/groups/opt_out.


[JIRA] [jenkins-multijob-plugin] (JENKINS-21615) MultiJob 1.11 phases broken when upgraded from 1.9

2014-02-02 Thread a...@tikalk.com (JIRA)














































Alex Nickolaevsky
 commented on  JENKINS-21615


MultiJob 1.11 phases broken when upgraded from 1.9















Hi, 
First issue: please provide more info regarding the configuration of multijob project and sub jobs projects.
Second: Stop phase execution on failure was the default behaviour in previous versions.
Thanks.



























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/groups/opt_out.