Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to adjust Jenkins weather report for clover coverage on PHP projects
    primarykey
    data
    text
    <p>I have a few PHP projects installed for a new team in Jenkins, and I'm trying to lower the expectations initially to help ramp them up on testing and everything. Initially we're shooting for 20% code coverage. I've adjusted the bounds in my PHPUnit config file to go green on code coverage when they hit 20% - so they can see they're heading in the right direction. but what I'm trying to do is update the weather report in my jenkins views to reflect the clover coverage as well, and I can't seem to do that!</p> <p><img src="https://i.stack.imgur.com/GGHho.png" alt="Jenkins Weather Report Clover Coverage"></p> <p>I have the <em>Publish Clover PHP Coverage Report</em> checked in my jenkins project configuration, and my clover.xml is being generated from PHPUnit, but I'm not sure how to adjust the bounds for this.</p> <p><strong>logging from phpunit.xml.dist:</strong></p> <pre><code>&lt;logging&gt; &lt;log type="coverage-html" target="build/coverage" title="ERC" charset="UTF-8" yui="true" highlight="true" lowUpperBound="10" highLowerBound="20"/&gt; &lt;log type="coverage-clover" target="build/logs/clover.xml"/&gt; &lt;log type="junit" target="build/logs/junit.xml" logIncompleteSkipped="false"/&gt; &lt;/logging&gt; </code></pre> <p><strong>Project settings coverage metrics</strong></p> <p>I initially didn't have the <em>Publish Html Report</em> enabled, but I've found that enabling it and modifying the percentages never had any affect after I saved and re-ran the build. <img src="https://i.stack.imgur.com/PEKYE.png" alt="enter image description here"></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload