We're trying to switch our Build Pipeline from the classic way (Multiple Jobs) to the new pipeline-as-code approach. In the past we've chained some jobs together. We had some parallel test jobs and each test has produced its own test results. These results were copied to the master job and there aggregated and displayed.
What is the best way to do this in a "real" pipeline? Can a call a JUnitResultArchiver step in each parallel Stage which has test results and the results will be combined or does it only displays the last recorded result? Do I have to do a similar aggregate task and call JUnitResultArchiver only once? I can imagine some of you have already resolved this issue as its a common one I would think. -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0a8cc24b-1b24-4875-b936-cabf6b56a1e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
