|
||||||||
|
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.
Hi Roni,
As you say it is possible to:
1) Create a multi-job at the create job page in jenkins
2) As a build step on the multi-job create a conditional buildstep
3) When that conditional buildstep is true run a multijob phase as part of the conditional build step.
This executes perfectly command wise having the desired effect from a run perspective.
The issue though is that the multi-job phase which is run when the conditional buildstep is true does not show up graphically on the multi-job graphical display, meaning an end user can not see that phase being executed unless you go to the console output.
So fixing the plug-in to display phases that are nested in a conditional build-step would greatly benefit end users who wish to see what exactly the multijob plugin is executing at build time without having to drill through to the console log. One of the main benefits the multijob brings is that graphical representation of chained jobs and giving the user the ability to see the plugin step through each job in the phase but that is lost if you call the multijob phase in the conditional build step.
Hope that makes sense. The other fix is great though regarding the parameters. However, fixing the view for conditional buildsteps would just make the plugin so much more powerfull.
Kind Regards, Steven