You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Gavin (Commented) (JIRA)" <ji...@apache.org> on 2012/02/25 22:37:48 UTC

[jira] [Commented] (INFRA-4491) Clover code coverage reports no longer working on Jenkins

    [ https://issues.apache.org/jira/browse/INFRA-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216546#comment-13216546 ] 

Gavin commented on INFRA-4491:
------------------------------

The Clover plugin was there, just disabled, no idea why.
I have enabled the plugin again so try again and we'll see if any issues crop up.

Note the license and Clover jar files etc that you use are located on the lucene zone and maintained by the lucene pmc, should anything be wrong with that part of it.
                
> Clover code coverage reports no longer working on Jenkins
> ---------------------------------------------------------
>
>                 Key: INFRA-4491
>                 URL: https://issues.apache.org/jira/browse/INFRA-4491
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Jenkins
>            Reporter: Uwe Schindler
>            Assignee: Gavin
>
> Since a few weeks, Jenkins' Clover code coverage reports are no longer showing up on reports and cannot be configured in configuration options. It seems, that the plugin iss missing since the major outtages recently. In fact all LUCENE and SOLR freestyle builds run their Clover test form their sh scripts, but the clover.xml and HTML reports from the build dirs are no longer collected and published.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira