Hey jeff,<br><br>I took the patch and reworked it a bit to fit in with our thinking.&nbsp; It&#39;s in there.<br><br>After talking to alex we decided that it should be the builds responsibility to put builds into the artifacts directory.&nbsp; For example in our builds, we have 
<br><br>desc &#39;Continuous build target&#39;<br>task :cruise =&gt; [&#39;test:units:rcov&#39;, &#39;test:functionals:rcov&#39;, &#39;test:integration&#39;] do <br>&nbsp; out = ENV[&#39;CC_BUILD_ARTIFACTS&#39;] || &#39;out&#39;
<br>&nbsp; mv &#39;coverage/units&#39;, &quot;#{out}/unit test coverage&quot;<br>&nbsp; mv &#39;coverage/functionals&#39;, &quot;#{out}/functional test coverage&quot;<br>end<br><br>anything extra in the artifacts directory will get a link generated for it and put into the build page - look at unit test coverage &amp; functional test coverage at 
<br><br><a href="http://cruisecontrolrb.thoughtworks.com/builds/CruiseControl/181">http://cruisecontrolrb.thoughtworks.com/builds/CruiseControl/181</a><br><br>putting a link into CC_HOME/public dir won&#39;t work under windows, but we do need it, so there&#39;s an artifact action in the builds_controller now.&nbsp; it is basically a passthrough for build artifacts, such that links like :
<br><br><a href="http://cruisecontrolrb.thoughtworks.com/builds/CruiseControl/181/unit+test+coverage/app-controllers-application_rb.html">http://cruisecontrolrb.thoughtworks.com/builds/CruiseControl/181/unit+test+coverage/app-controllers-application_rb.html
</a><br><br>work as expected.<br><br>ask me if anyone has any questions.&nbsp; Jeff we should talk about how we can get a thicker band of communication going between us here and you there.<br><br>Jeremy<br><br><div><span class="gmail_quote">
On 2/7/07, <b class="gmail_sendername">Jeff Xiong</b> &lt;<a href="mailto:gigix1980@gmail.com">gigix1980@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi there. I tried to integrate rcov reports. I selected the simplest<br>solution: symbol-link the build artifacts directories into<br>$CC_HOME/public directory, so that users can access rcov reports<br>directly. The attachment is my modifications of the source code.
<br><br>--<br>Jeff Xiong<br>Software Journeyman<br><br>_______________________________________________<br>Cruisecontrolrb-developers mailing list<br><a href="mailto:Cruisecontrolrb-developers@rubyforge.org">Cruisecontrolrb-developers@rubyforge.org
</a><br><a href="http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers">http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers</a><br><br><br></blockquote></div><br>