[workflow-plugin] JUnit Tests Aggregation

[Pedro Algarvio]

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.

Has anyone achieved this with the workflow plugin which could point me in the right direction?

I also created a ticket because I need the ghprb trigger in my job, https://issues.jenkins-ci.org/browse/JENKINS-26591

This is not currently supported right?

Thanks!

Pedro Algarvio.

[sebastien....@gmail.com]

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

[Pedro Algarvio]

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

[Jesse Glick]

On Monday, February 16, 2015 at 1:08:42 PM UTC-5, Pedro Algarvio wrote:

I need to be able to trigger builds from GitHub hooks, which is not yet supported I believe

 Not clear if you are talking about JENKINS-26591 [1], for the pull-request builder, or general GitHub push hooks, which would probably need to be filed as a separate issue and linked [2].

[1] https://issues.jenkins-ci.org/browse/JENKINS-26591

[2] https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md#triggers

[Pedro Algarvio]

I was the one filing https://issues.jenkins-ci.org/browse/JENKINS-26591 for GHPRB and I also filed https://issues.jenkins-ci.org/browse/JENKINS-27136 for the general github push hooks

I need both for my projects.