or you can configure the job to archive those files as another artifact (for instance, &quot;log-files.zip&quot;) and then download it from hudson. (without accessing the hudson server). <br><br><br><div class="gmail_quote">
On Sat, Aug 13, 2011 at 9:49 AM, Lukas Renggli <span dir="ltr">&lt;<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
builder.sh writes &quot;PharoDebug.log&quot; and since recently also &quot;crash.dmp&quot;<br>
to the error console, so that Jenkins displays them in the build log.<br>
Also you can find all build-artifacts (such as PharoDebug.log and<br>
crash.dmp) in the workspace.<br>
<br>
Lukas<br>
<div><div></div><div class="h5"><br>
On 13 August 2011 14:30, Mariano Martinez Peck &lt;<a href="mailto:marianopeck@gmail.com">marianopeck@gmail.com</a>&gt; wrote:<br>
&gt; because a test is red and I don&#39;t have enough information with the small<br>
&gt; stack show in Hudson.<br>
&gt;<br>
&gt; THanks<br>
&gt;<br>
&gt; --<br>
&gt; Mariano<br>
&gt; <a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br>
&gt;<br>
&gt;<br>
<br>
<br>
<br>
</div></div><font color="#888888">--<br>
Lukas Renggli<br>
<a href="http://www.lukas-renggli.ch" target="_blank">www.lukas-renggli.ch</a><br>
<br>
</font></blockquote></div><br>