Hello, I'm having problems with collecting results from jobs run in parallel (as in pipeline 'parallel') as not all the test results gets collected; Can you explain what can go wrong and how to fix it? Thanks Ferruccio
On Friday, 20 May 2016 08:12:38 UTC+1, Lars Meynberg wrote: > > Ok it is possible to call JUnitResultArchiver more than once and all > recorded test results will be integrated. But to capture all results > accordingly you have to be careful about when to do it. Especially if > you're working with try/catch/finally. On some catches I was not at the > same node workspace anymore even all was in the same node step. > > Am Mittwoch, 18. Mai 2016 15:14:55 UTC+2 schrieb Lars Meynberg: >> >> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/429cf9d1-5f2f-4f3a-b615-7458b340eef6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
