Seems to be pulling in too much information - Not respecting my decision for relative path

[JasonSmiley]

So I am generating 3 different reports for this tool

1) the Full run report (1st run of suite) - has its own directory - target/artifacts/target/full-reports/ 2) the Rerun report (2nd run of failed tests) - has its own directory - target/artifacts/target/rerun-reports/ 3) the latest report (most recent run) - has its own directory - target/artifacts/targat/jenkins-reports/

I want the cucumber report to only look at the results in the 3rd directory, however, it seems to be pulling them all. (I see the test names appearing 3 times in the report)

I am probably doing something wrong but your documentation doesn't specify how to set the directory. Only that it can be set.

I am currently doing this:

target/artifacts/targat/jenkins-reports/

But this is pulling everything instead of only what I asked. Is this a bug or am I doing something wrong?

[kingsleyh]

Read the last section about notes on configuration and let me know if that doesn't help https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java/wiki/Detailed-Configuration

Sent from my iPhone

On 15 Oct 2014, at 22:33, JasonSmiley notifications@github.com wrote:

So I am generating 3 different reports for this tool

1) the Full run report (1st run of suite) - has its own directory - target/artifacts/target/full-reports/ 2) the Rerun report (2nd run of failed tests) - has its own directory - target/artifacts/target/rerun-reports/ 3) the latest report (most recent run) - has its own directory - target/artifacts/targat/jenkins-reports/

I want the cucumber report to only look at the results in the 3rd directory, however, it seems to be pulling them all. (I see the test names appearing 3 times in the report)

I am probably doing something wrong but your documentation doesn't specify how to set the directory. Only that it can be set.

I am currently doing this:

target/artifacts/targat/jenkins-reports/

But this is pulling everything instead of only what I asked. Is this a bug or am I doing something wrong?

— Reply to this email directly or view it on GitHub.

[JasonSmiley]

You can close this. I figured out the issue. it was on my end....

Sorry! (Also, your documentation is pretty bad, I would change the image to be more reflective of what you are trying to say - my biggest concern as that the image and the doc were telling me two different things. One say "/target/" but the image said "target/" - but at least you made me double check the workspace directory! :) )

[kingsleyh]

Glad you got it working. I'm not aware of any documentation or image that says /target/

Sent from my iPhone

On 16 Oct 2014, at 15:35, JasonSmiley notifications@github.com wrote:

You can close this. I figured out the issue. it was on my end....

Sorry! (Also, your documentation is pretty bad, I would change the image to be more reflective of what you are trying to say - my biggest concern as that the image and the doc were telling me two different things. One say "/target/" but the image said "target/" - but at least you made me double check the workspace directory! :) )

— Reply to this email directly or view it on GitHub.

[JasonSmiley]

Alright, this problem came back.

Just to re-iterate:

I am generating 3 different reports for this tool

1) the Full run report (1st run of suite) - has its own directory - target/full-reports/ 2) the Rerun report (2nd run of failed tests) - has its own directory - target/rerun-reports/ 3) the latest report (most recent run) - has its own directory - target/jenkins-reports/

In the path field, I have "target/jenkins-reports/", but when I have to perform a rerun, the test is marked as failing even though all tests passed during the re-run.

I am executing using a ruby rake file which basically runs "mvn clean test" twice. The first time using the cucumber options passed in, and the second time using rerun.txt.

When I view the report, I am seeing the suite 3 times - it looks like all 3 .json files are being pulled in (summary view), however, when I click a report, it only shows me one set of results (re-run report / latest report)

[kingsleyh]

Using master only or on a slave?

Sent from my iPhone

On 22 Oct 2014, at 22:24, JasonSmiley notifications@github.com wrote:

Alright, this problem came back.

— Reply to this email directly or view it on GitHub.

[JasonSmiley]

Its on a slave now, that could be why.

Log snippet:

[CucumberReportPublisher] copying json from: file:/jenkins/workspace/Selenium%20Grid%20Site%20Search%20Smoke%20Tests%20(QA)/to reports directory: file:/var/lib/jenkins/jobs/Selenium%20Grid%20Site%20Search%20Smoke%20Tests%20(QA)/builds/2014-10-22_16-01-19/cucumber-html-reports/ [CucumberReportPublisher] Generating HTML reports Build step 'Publish cucumber results as a report' marked build as failure

As you can see, its not using the path I specified.

[kingsleyh]

I think perhaps the config is not respected on the slave - I remember an issue about that a while ago.

Sent from my iPhone

On 22 Oct 2014, at 22:44, JasonSmiley notifications@github.com wrote:

Its on a slave now, that could be why:

Log snippet:

[CucumberReportPublisher] copying json from: file:/jenkins/workspace/Selenium%20Grid%20Site%20Search%20Smoke%20Tests%20(QA)/to reports directory: file:/var/lib/jenkins/jobs/Selenium%20Grid%20Site%20Search%20Smoke%20Tests%20(QA)/builds/2014-10-22_16-01-19/cucumber-html-reports/ [CucumberReportPublisher] Generating HTML reports Build step 'Publish cucumber results as a report' marked build as failure

As you can see, its not using the path I specified.

— Reply to this email directly or view it on GitHub.

[JasonSmiley]

Should I take my jobs off the slave for now and just wait for a code fix? (I noticed earlier that this worked when I was running on master)

[kingsleyh]

well it’s up to you - I’m not sure when a code fix will emerge. I’ll try to have a look at the weekend - but I can’t promise anything.

—K

On 22 Oct 2014, at 22:54, JasonSmiley notifications@github.com wrote:

Should I take my jobs off the slave for now and just wait for a code fiz?

— Reply to this email directly or view it on GitHub https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java/issues/109#issuecomment-60162123.

[JasonSmiley]

I appreciate your honesty :)

I'll work something out with the rest of the developer team.

[JasonSmiley]

Hi Kingsleyh,

Just wanted to get a status update - wasn't sure if I should just re-do my reporting or not.

[damianszczepanik]

Recently this part of the plugin was completlly refactored and issue should be gone