Yeah, that's what I was looking for.
But the other option is good for the builds which failed in the past...
Christian
On Tue, Oct 30, 2012 at 11:29 PM, David Karlsen wrote:
> Another [maybe more obvious] option (for more ad-hoc stuff) is to
> browse the workspace - but that will only contain th
Another [maybe more obvious] option (for more ad-hoc stuff) is to
browse the workspace - but that will only contain the current
situation and not the history.
2012/10/30 Christian Müller :
> Thanks for the hint David!
> I configured the Camel.2.10.x.fulltest to archive the log files too.
>
> Thank
Thanks for the hint David!
I configured the Camel.2.10.x.fulltest to archive the log files too.
Thanks again,
Christian
On Tue, Oct 30, 2012 at 10:09 AM, David Karlsen wrote:
> You could configure the job to archive the log-files - then they
> should appear under archived artifacts.
>
> 2012/10/
You could configure the job to archive the log-files - then they
should appear under archived artifacts.
2012/10/30 Christian Müller :
> Hello Dan, hello list,
>
> do you know whether there is a way to access the Camel log files on
> build.apache.org even I'm not a Jenkins admin? I'm asking becaus
