|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I came to the same conclusion / workaround. Both plugins have display issues but the ability to parallelize many jobs is the killer feature that keeps bringing back to the multi-job.
To me, it seems like simple cases, like this one job kicks of this one job (like the picture at https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin), work well, but complex cases that have jobs that kick off multiple jobs, not so much.
If only someone savvier than I could combine the two.