404 when I click on the Cucumber Reports links

[cammer-alchemy]

I'm trying to get my reports to show up, but end up with a 404. I installed the cucumber-reports plugin that's available via the Jenkins Plugin Manager, which is currently version 0.0.20. Then, I set my build step up as follows:

source /opt/boxen/env.sh rbenv local 1.9.3-p392 cp config/database.yml.boxen config/database.yml bundle install bundle exec cucumber --format json -o cucumber.json features

Then, I selected the post-build action 'Publish cucumber results as a report', and left all of the options as their default. The output was as follows:

.... 34 scenarios (34 passed) 342 steps (342 passed) 3m21.302s Coverage report generated for Cucumber Features to /Users/ryanc/.jenkins/jobs/cucumber_test_1/workspace/coverage/cucumber. 3114 / 7994 LOC (38.95%) covered. [CucumberReportPublisher] Compiling Cucumber Html Reports ... [CucumberReportPublisher] detected this build is running on the master [CucumberReportPublisher] copying json to reports directory: /Users/ryanc/.jenkins/jobs/cucumber_test_1/builds/2013-03-20_17-47-51/cucumber-html-reports [CucumberReportPublisher] Generating HTML reports Finished: SUCCESS

However, when I click on the Cucumber Reports link, I'm taken to:

http://localhost:8080/job/cucumber_test_1/13/cucumber-html-reports/?

or, if I click on the Cucumber Reports link on the project page:

http://localhost:8080/job/cucumber_test_1/cucumber-html-reports/?

The output is:

Status Code: 404

Exception: Stacktrace: (none)

Generated by Winstone Servlet Engine v0.9.10 at Wed Mar 20 18:20:26 PDT 2013

The workspace contains a file, cucumber.json, as well as a directory, coverage/cucumber, as well as a directory, jobs/cucumber_test_1/builds/2013-03-20_17-47-51, which contains a folder, cucumber-html-reports.

Does that provide enough context?

[kingsleyh]

Hi

could you try pasting your cucumber.json file into the diagnostic tool here: http://cucumber-reporting.masterthought.net/ and let me know the results.

also you can read further information about the plugin here: http://masterthought.net/section/cucumber-reporting

Thanks

--K

On 21 Mar 2013, at 01:25, Ryan Cammer notifications@github.com wrote:

I'm trying to get my reports to show up, but end up with a 404. I installed the cucumber-reports plugin that's available via the Jenkins Plugin Manager, which is currently version 0.0.20. Then, I set my build step up as follows:

source /opt/boxen/env.sh rbenv local 1.9.3-p392 cp config/database.yml.boxen config/database.yml bundle install bundle exec cucumber --format json -o cucumber.json features

Then, I selected the post-build action 'Publish cucumber results as a report', and left all of the options as their default. The output was as follows:

.... 34 scenarios (34 passed) 342 steps (342 passed) 3m21.302s Coverage report generated for Cucumber Features to /Users/ryanc/.jenkins/jobs/cucumber_test_1/workspace/coverage/cucumber. 3114 / 7994 LOC (38.95%) covered. [CucumberReportPublisher] Compiling Cucumber Html Reports ... [CucumberReportPublisher] detected this build is running on the master [CucumberReportPublisher] copying json to reports directory: /Users/ryanc/.jenkins/jobs/cucumber_test_1/builds/2013-03-20_17-47-51/cucumber-html-reports [CucumberReportPublisher] Generating HTML reports Finished: SUCCESS

However, when I click on the Cucumber Reports link, I'm taken to:

http://localhost:8080/job/cucumber_test_1/13/cucumber-html-reports/?

or, if I click on the Cucumber Reports link on the project page:

http://localhost:8080/job/cucumber_test_1/cucumber-html-reports/?

The output is:

Status Code: 404

Exception: Stacktrace: (none)

Generated by Winstone Servlet Engine v0.9.10 at Wed Mar 20 18:20:26 PDT 2013

The workspace contains a file, cucumber.json, as well as a directory, coverage/cucumber, as well as a directory, jobs/cucumber_test_1/builds/2013-03-20_17-47-51, which contains a folder, cucumber-html-reports.

Does that provide enough context?

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

[cammer-alchemy]

No problem! Here's the abbreviated output:

Feature Overview for Build: 1

The following graph shows passing and failing statistics for features in this build:

Feature Statistics

Scenarios Steps
Feature Total Passed Failed Total Passed Failed Skipped Pending Duration Status ( removed ) 0 0 0 0 0 0 0 0 0 ms passed ( removed ) 1 1 0 19 19 0 0 0 0 ms passed ( removed ) 2 2 0 13 13 0 0 0 0 ms passed ( removed ) 6 6 0 56 56 0 0 0 0 ms passed ( removed ) 6 6 0 96 96 0 0 0 0 ms passed ( removed ) 2 2 0 33 33 0 0 0 0 ms passed ( removed ) 2 2 0 39 39 0 0 0 0 ms passed ( removed ) 1 1 0 18 18 0 0 0 0 ms passed ( removed ) 3 3 0 24 24 0 0 0 0 ms passed ( removed ) 6 6 0 49 49 0 0 0 0 ms passed ( removed ) 5 5 0 32 32 0 0 0 0 ms passed ( removed ) 0 0 0 0 0 0 0 0 0 ms passed 12 34 34 0 379 379 0 0 0 0 ms Totals

[kingsleyh]

So it looks to me as if the report generation was ok - the report was generated successfully via the diagnostic tool without any issues.

When you navigate to the file system: /Users/ryanc/.jenkins/jobs/cucumber_test_1/builds/2013-03-20_17-47-51/cucumber-html-reports

what is inside that cucumber-html-reports directory? it should contain a feature-overview.html and other files. If all the files are there than something weird is happening with the urls

--K

On 21 Mar 2013, at 21:57, Ryan Cammer notifications@github.com wrote:

No problem! Here's the abbreviated output:

Feature Overview for Build: 1

The following graph shows passing and failing statistics for features in this build:

Feature Statistics

Scenarios Steps

Feature Total Passed Failed Total Passed Failed Skipped Pending Duration Status ( removed ) 0 0 0 0 0 0 0 0 0 ms passed ( removed ) 1 1 0 19 19 0 0 0 0 ms passed ( removed ) 2 2 0 13 13 0 0 0 0 ms passed ( removed ) 6 6 0 56 56 0 0 0 0 ms passed ( removed ) 6 6 0 96 96 0 0 0 0 ms passed ( removed ) 2 2 0 33 33 0 0 0 0 ms passed ( removed ) 2 2 0 39 39 0 0 0 0 ms passed ( removed ) 1 1 0 18 18 0 0 0 0 ms passed ( removed ) 3 3 0 24 24 0 0 0 0 ms passed ( removed ) 6 6 0 49 49 0 0 0 0 ms passed ( removed ) 5 5 0 32 32 0 0 0 0 ms passed ( removed ) 0 0 0 0 0 0 0 0 0 ms passed 12 34 34 0 379 379 0 0 0 0 ms Totals

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

[cammer-alchemy]

find . . ./coverage ./coverage/cucumber ./coverage/cucumber/.last_run.json ./coverage/cucumber/.resultset.json ./coverage/cucumber/assets ./coverage/cucumber/assets/0.7.1 ./coverage/cucumber/assets/0.7.1/application.css ./coverage/cucumber/assets/0.7.1/application.js ./coverage/cucumber/assets/0.7.1/fancybox ./coverage/cucumber/assets/0.7.1/fancybox/blank.gif ./coverage/cucumber/assets/0.7.1/fancybox/fancy_close.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_loading.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_nav_left.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_nav_right.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_e.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_n.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_ne.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_nw.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_s.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_se.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_sw.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_w.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_title_left.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_title_main.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_title_over.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_title_right.png ./coverage/cucumber/assets/0.7.1/fancybox/fancybox-x.png ./coverage/cucumber/assets/0.7.1/fancybox/fancybox-y.png ./coverage/cucumber/assets/0.7.1/fancybox/fancybox.png ./coverage/cucumber/assets/0.7.1/favicon_green.png ./coverage/cucumber/assets/0.7.1/favicon_red.png ./coverage/cucumber/assets/0.7.1/favicon_yellow.png ./coverage/cucumber/assets/0.7.1/loading.gif ./coverage/cucumber/assets/0.7.1/magnify.png ./coverage/cucumber/assets/0.7.1/smoothness ./coverage/cucumber/assets/0.7.1/smoothness/images ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_flat_75_ffffff_40x100.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_65_ffffff_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_75_dadada_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_222222_256x240.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_2e83ff_256x240.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_454545_256x240.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_888888_256x240.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_cd0a0a_256x240.png ./coverage/cucumber/index.html ./cucumber.json

[kingsleyh]

ok - can you try running without the coverage? that seems to be possibly causing an issue?

--K

On 22 Mar 2013, at 22:09, Ryan Cammer notifications@github.com wrote:

find . . ./coverage ./coverage/cucumber ./coverage/cucumber/.last_run.json ./coverage/cucumber/.resultset.json ./coverage/cucumber/assets ./coverage/cucumber/assets/0.7.1 ./coverage/cucumber/assets/0.7.1/application.css ./coverage/cucumber/assets/0.7.1/application.js ./coverage/cucumber/assets/0.7.1/fancybox ./coverage/cucumber/assets/0.7.1/fancybox/blank.gif ./coverage/cucumber/assets/0.7.1/fancybox/fancy_close.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_loading.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_nav_left.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_nav_right.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_e.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_n.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_ne.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_nw.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_s.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_se.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_sw.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_shadow_w.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_title_left.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_title_main.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_title_over.png ./coverage/cucumber/assets/0.7.1/fancybox/fancy_title_right.png ./coverage/cucumber/assets/0.7.1/fancybox/fancybox-x.png ./coverage/cucumber/assets/0.7.1/fancybox/fancybox-y.png ./coverage/cucumber/assets/0.7.1/fancybox/fancybox.png ./coverage/cucumber/assets/0.7.1/favicon_green.png ./coverage/cucumber/assets/0.7.1/favicon_red.png ./coverage/cucumber/assets/0.7.1/favicon_yellow.png ./coverage/cucumber/assets/0.7.1/loading.gif ./coverage/cucumber/assets/0.7.1/magnify.png ./coverage/cucumber/assets/0.7.1/smoothness ./coverage/cucumber/assets/0.7.1/smoothness/images ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_flat_75_ffffff_40x100.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_65_ffffff_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_75_dadada_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_222222_256x240.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_2e83ff_256x240.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_454545_256x240.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_888888_256x240.png ./coverage/cucumber/assets/0.7.1/smoothness/images/ui-icons_cd0a0a_256x240.png ./coverage/cucumber/index.html ./cucumber.json

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

[sethvargo]

I'm seeing the same thing. The only thing that shows up in my cucumber-html-reports directory is cucumber.json. I used the online tool and it generated the report just fine. The build succeeds and says it generated the report, but doesn't. :frowning:

[kingsleyh]

can you try to set the advanced section json reports path - to the directory in the workspace where the json file goes relative to the workspace.

e.g. if you look in the job workspace and see the cucumber.json in src/output then enter src/output into the json reports path and try again. Try to make sure there are no other json files in the same directory as the cucumber.json in the workspace also.

The only thing I can think of is that there are other json files being found which are causing an error internally.

--K

On 28 Mar 2013, at 17:21, Seth Vargo notifications@github.com wrote:

I'm seeing the same thing. The only thing that shows up in my cucumber-html-reports directory is cucumber.json. I used the online tool and it generated the report just fine. The build succeeds and says it generated the report, but doesn't.

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

[sethvargo]

Tried that too. cucumber.json is at the root of my project. I tried specifying the full path (/var/lib/jenkins/workspace), but that didn't work either. There are no other JSON files in the project.

[kingsleyh]

hmm - which version of jenkins are you using? I haven't seen this problem before - it's very strange.

On 28 Mar 2013, at 17:33, Seth Vargo notifications@github.com wrote:

Tried that too. cucumber.json is at the root of my project. I tried specifying the full path (/var/lib/jenkins/workspace), but that didn't work either. There are no other JSON files in the project.

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

[sethvargo]

1.480.3

[kingsleyh]

hmm - I have version 1.504 and it's working there - perhaps you can try upgrading to 1.504. If I get some time I could try to install your version of jenkins and see if I find the same issue.

--K

On 28 Mar 2013, at 17:36, Seth Vargo notifications@github.com wrote:

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

[sethvargo]

This is the version I got when I install Jenkins via apt (Ubuntu 12.10)…

Thanks, Seth

[kingsleyh]

download this one: http://mirrors.jenkins-ci.org/war/1.504/jenkins.war

then do: java -jar jenkins.war and navigate to http://localhost:8080 and try running on that and see if it makes any difference.

you'll have to stop your other jenkins probably - but if .jenkins (jenkins_home) is in your home dir from the ubuntu installed one then your jobs will appear ok - otherwise you might have to add the job again.

let me know if it works for you that way? if it does - then it's the jenkins version thats causing the issue.

--K

On 28 Mar 2013, at 17:40, Seth Vargo notifications@github.com wrote:

This is the version I got when I install Jenkins via apt (Ubuntu 12.10)…

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

[sethvargo]

No change:

[CucumberReportPublisher] Compiling Cucumber Html Reports ... [CucumberReportPublisher] detected this build is running on the master [CucumberReportPublisher] copying json to reports directory: /var/lib/jenkins/jobs/a_heimann-phase_3/builds/2013-03-28_17-50-41/cucumber-html-reports [CucumberReportPublisher] Generating HTML reports Finished: SUCCESS

Then:

On Mar 28, 2013, at 1:46 PM, Kingsley Hendrickse notifications@github.com wrote:

download this one: http://mirrors.jenkins-ci.org/war/1.504/jenkins.war

then do: java -jar jenkins.war and navigate to http://localhost:8080 and try running on that and see if it makes any difference.

you'll have to stop your other jenkins probably - but if .jenkins (jenkins_home) is in your home dir from the ubuntu installed one then your jobs will appear ok - otherwise you might have to add the job again.

let me know if it works for you that way? if it does - then it's the jenkins version thats causing the issue.

--K

On 28 Mar 2013, at 17:40, Seth Vargo notifications@github.com wrote:

This is the version I got when I install Jenkins via apt (Ubuntu 12.10)…

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

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

[kingsleyh]

ok try this:

wget http://www.masterthought.net/system/uploads/original_cucumber-reports-0.0.20.hpi

mv original_cucumber-reports-0.0.20.hpi cucumber-reports-0.0.20.hpi

then cd .jenkins/plugins and rm -rf cucumber-reports*

now copy the cucumber-reports hpi you downloaded into the .jenkins/plugins dir and restart jenkins and see if that makes any difference

--K

On 28 Mar 2013, at 17:40, Seth Vargo notifications@github.com wrote:

This is the version I got when I install Jenkins via apt (Ubuntu 12.10)…

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

[kingsleyh]

also make sure you are using a freestyle project type job in jenkins

On 28 Mar 2013, at 17:40, Seth Vargo notifications@github.com wrote:

This is the version I got when I install Jenkins via apt (Ubuntu 12.10)…

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

[kingsleyh]

hi - did you manage to get this working?

[sethvargo]

No, I gave up and manually review the cucumber reports now

This message was sent from my mobile device.

I apologize in advance for any typographical errors or autocorrections.

On Apr 13, 2013, at 6:21 AM, Kingsley Hendrickse notifications@github.com wrote:

hi - did you manage to get this working?

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

[kingsleyh]

I haven't seen this problem before - but it's very strange. The fact that the report is correctly generated via the diagnostics tool points to something either within the jenkins plugin itself or related to something environmental on your side. Since I can't reproduce and the report generation part works I can't really help much more so closing this for now - If I spot something in the future I will try to fix it

[jonatask]

Kingsley,

Sorry for reopening this but I've been facing the same problem. Any idea about how to solve?

Thanks.

[kingsleyh]

Could there be a non cucumber json file getting picked up as well?

Sent from my iPhone

On 20 Nov 2014, at 00:56, jonatask notifications@github.com wrote:

Kingsley,

Sorry for reopening this but I've been facing the same problem. Any idea about how to solve?

Thanks.

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

[jonatask]

Solved. I had typed a tag with "/" in the feature file, like @11/11/2014 Then it went to the junit and json files. Once there, Cucumber report thinks it's a directory.

Thanks.