Quantcast

Pending pull request #501 for parsing JUnit reports

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Pending pull request #501 for parsing JUnit reports

Anne Stellingwerf-2
Hi all,

I'd like to ask you to have a look at my pull request (https://github.com/jenkinsci/jenkins/pull/501/). It aims to expand axes from multi-config jobs when determining what reports to parse.
We have a job where we have a component names axis ($component / %component%), and for all components we want to execute tests and then parse the result. It now parses cumulatively when the pattern is similar to ./components/*/tests/results/*.xml, but ./components/$component/tests/results/*.xml didn't work yet.

I fixed that in this patch. Will you please consider pulling this?

Kind regards,
Anne Stellingwerf
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Pending pull request #501 for parsing JUnit reports

Anne Stellingwerf-2
Echo...

On Sat, Jun 30, 2012 at 11:12 AM, Anne Stellingwerf <[hidden email]> wrote:
Hi all,

I'd like to ask you to have a look at my pull request (https://github.com/jenkinsci/jenkins/pull/501/). It aims to expand axes from multi-config jobs when determining what reports to parse.
We have a job where we have a component names axis ($component / %component%), and for all components we want to execute tests and then parse the result. It now parses cumulatively when the pattern is similar to ./components/*/tests/results/*.xml, but ./components/$component/tests/results/*.xml didn't work yet.

I fixed that in this patch. Will you please consider pulling this?

Kind regards,
Anne Stellingwerf

Loading...