On February 16, 2015 10:02:15 AM GMT, [email protected] wrote: >Hello Pedro, > >On Monday, January 26, 2015 at 1:57:36 AM UTC+1, Pedro Algarvio wrote: >> >> I've only started to read through the documentation and have not yet >dig >> in to get a workflow job configured because I fail to see support for >some >> needed features and/or plugins, one of which is junit tests >aggregation. >> > >This tutorial explains how to use the junit plugin from workflow: >https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md#recording-test-results-and-artifacts > >I just converted one matrix project to workflow with this groovy >script: > >String[] release_types = ['debug', 'release'] >for (int i = 0; i < release_types.size(); ++i) { > String release_type = release_types[i] > node("qibuild-linux64") { > echo "release_type: ${release_type}" > env.release_type = release_type > sh "build.py" > step([$class: 'JUnitResultArchiver', testResults: 'tests/*/*.xml']) > } >} > >I does work: tests are run for both values of "release_type" and their >results get aggregated. > >However, I've not found yet how to "tag" the tests with the >corresponding >"release_type", as matrix does. Sso currently when one test fails, I >don't >know if it was from the release or debug run. (I can find it out by >checking the log though). > >hope it helps. > >Sebastien > >-- >You received this message because you are subscribed to a topic in the >Google Groups "Jenkins Users" group. >To unsubscribe from this topic, visit >https://groups.google.com/d/topic/jenkinsci-users/w7sQoN53Lu4/unsubscribe. >To unsubscribe from this group and all its topics, send an email to >[email protected]. >To view this discussion on the web visit >https://groups.google.com/d/msgid/jenkinsci-users/172d28d4-40fd-4952-bf48-a5e3a4aa1ea8%40googlegroups.com. >For more options, visit https://groups.google.com/d/optout.
Hello Sebastien. Thank you for your reply. I'm really interested on getting the aggregated results but I also need to know where they are coming from, similar to your debug vs release dilemma. I've also kind of set aside the workflow plugin because I need to be able to trigger builds from GitHub hooks, which is not yet supported I believe.... Best, Pedro. Pedro Algarvio @ Phone -- 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/356EFEE4-3250-4A2A-B4DD-FB98F3A952D6%40algarvio.me. For more options, visit https://groups.google.com/d/optout.
