Pipeline, parallel, and junit = broken

[Thorsten Meinl]

I've read on several places that matrix jobs in pipeline are replaced by the "parallel" step. However, this doesn't work at all with junit tests. We have a bunch of JUnit tests that are tested on different OS. They are exactly the same tests for all OS, hence also the output file names are identical. This wasn't a problem with matrix jobs because every axis was treated as an independent job and you could easily browser the tests for every configuration. With a parallel pipeline this isn't possible because all result files collect by "junit" are thrown together which makes it impossible to distinguish and also sometimes the display is just wrong (depending on which parallel branch is collected the last). In short, parallel is totally useless in such cases.
Now I'm wondering if there are any plans to address this issue (I guess many users have the same problem) or if there is another approach to run the same tests on several OS with a pipeline job.

[Daniel Beck]

> On 03.02.2017, at 17:48, Thorsten Meinl <thorste...@knime.com> wrote:
>
> also sometimes the display is just wrong (depending on which parallel branch is collected the last).

This could be https://github.com/jenkinsci/junit-plugin/pull/63 which will be fixed in the next JUnit plugin release.

[Stephen Connolly]

Or https://github.com/jenkinsci/junit-plugin/pull/64

Which needs deciding...

Or bobby's version of similar idea https://github.com/jenkinsci/junit-plugin/pull/27

Both of those are not decided yet and need some discussion...

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2641DB23-1843-4704-B87C-0100BEC5F5F4%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--

Sent from my phone