Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I just figured it out with some help from the author. The trick is to escape the XML inside the XML and use <code>&lt;system-out&gt;</code>to feed the Measurements Plot plugin. The steps below shows how to use it and feed various values into the plugin:</p> <ol> <li>Create a New Job in Jenkins "free-style software project"</li> <li>Add String Parameter VALUETEST</li> <li>Add Build step Execute Shell Command is the code below.</li> <li>Add Post-build Action: Publish JUnit <ol> <li>Test report XMLs: testdetail-*.xml</li> <li>Check Retain long staandard output</li> <li>Check Measurement Plots</li> </ol></li> <li>Save and Build Now.</li> <li>Plot will appear under Test Results. You need more than one run for the plot appear.</li> </ol> <p>Execute Shell Command:</p> <pre><code>echo '&lt;?xml version="1.0" encoding="UTF-8"?&gt;' &gt; testdetail-lcov.xml echo '&lt;testsuites name="CodeAnalysis" tests="2" failures="0" disabled="0" errors="0" time="0"&gt;' &gt;&gt; testdetail-lcov.xml echo '&lt;testsuite name="Suite" tests="1" &gt;' &gt;&gt; testdetail-lcov.xml echo '&lt;testcase name="Case" status="run" time="0" classname="Suite"&gt;' &gt;&gt; testdetail-lcov.xml echo '&lt;/testcase&gt;&lt;/testsuite&gt;' &gt;&gt; testdetail-lcov.xml echo '&lt;testsuite tests="1" &gt;' &gt;&gt; testdetail-lcov.xml echo '&lt;testcase name="Lcov" status="run" time="0" classname="CodeAnalysis.Coverage"&gt;' &gt;&gt; testdetail-lcov.xml echo '&lt;system-out&gt;' &gt;&gt; testdetail-lcov.xml echo "&amp;lt;measurement&amp;gt;&amp;lt;name&amp;gt;Line Coverage&amp;lt;/name&amp;gt;&amp;lt;value&amp;gt;$VALUETEST&amp;lt;/value&amp;gt;&amp;lt;/measurement&amp;gt;" &gt;&gt; testdetail-lcov.xml echo '&lt;/system-out&gt;' &gt;&gt; testdetail-lcov.xml echo '&lt;/testcase&gt;&lt;/testsuite&gt;&lt;/testsuites&gt;' &gt;&gt; testdetail-lcov.xml </code></pre>
 

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