-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Hudson version 1.349 installed on Windows Server 2003 Standard Edition SP2 machine under Tomcat version 6.0.24. Browser opened on Windows XP Pro Version 2002 SP3 machine using IE 7.0.5730.13.
When integrating Clover reporting to a job, after the job has successfully built and Clover reports are generated, when clicking on the Job Name link in a view, the Coverage Report link located on the left side of the page (URL example: http://SERVERNAME/view/Testing/job/JOBNAME/clover/) does not contain the build number and therefore when you click the link you get a page with 404 error:
HTTP Status 404 -
type Status report
message
description The requested resource () is not available.
Apache Tomcat/6.0.24
navigating down to the specific build and then to the Clover Coverage Report link gets you to the proper pages.
The Generate an historical report and Generate a jwon report are checked within the Automatically record and report Clover Coverage in the job configuration. A proper license is entered. As well as the Publish Clover Coverage Report is manually configured correctly.
- is duplicated by
-
JENKINS-3461 Coverage report link returns HTTP 404 error
-
- Closed
-
In my case we do like this:
Publish Clover Coverage Report: build
Clover report file name: clover-coverage.xml (this file is generated by phpunit software during Phing build and stored at above location)
However we don't use Clover option "Automatically record and report Code Coverage using Clover.. Currently for Ant builds only." because our project is PHP type.
Let me know if you need more information.