Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGO7Ob1r-h15jSxdv1q+yeYgxy6kKaezYTaQT63-9sO=Z2p0sQ@mail.gmail.com>
References: 
 <CALvzYd8OE6qdo47zzZQfLhYOBM47ft4FvHHQvDBR4fonhHyhzg@mail.gmail.com>
	<CAGO7Ob0Y=WboOr0s+6hLXcHhNDub0XZ9KLX=ECz0riabRm_riQ@mail.gmail.com>
	<CALvzYd-q2E+B7t3Cv4CbjrJrM38fOafEnT74u_YPtrArr3aHxA@mail.gmail.com>
	<CAGO7Ob1r-h15jSxdv1q+yeYgxy6kKaezYTaQT63-9sO=Z2p0sQ@mail.gmail.com>
Date: Wed, 31 Oct 2012 00:12:22 +0100
Message-ID: 
 <CALvzYd_p4nMEbLyzJc5HpbyXG2BOZTyF2UXXFb_0Kt20zX=+mA@mail.gmail.com>
Subject: Re: Access log files on builds.apache.org
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: dev@camel.apache.org
Content-Type: multipart/alternative; boundary=20cf300fafe51c69ac04cd4eeb46

--20cf300fafe51c69ac04cd4eeb46
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <davidkarlsen@gmail.com>wro=
te:

> 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=FCller <christian.mueller@gmail.com>:
> > 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 <davidkarlsen@gmail.com
> >wrote:
> >
> >> You could configure the job to archive the log-files - then they
> >> should appear under archived artifacts.
> >>
> >> 2012/10/30 Christian M=FCller <christian.mueller@gmail.com>:
> >> > 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 because
> some
> >> of
> >> > the unit tests are brittle and are failing from time to time on our =
CI
> >> > server. Because we turned off the console logging by default, it's
> >> > difficult in some cases to figure out what went wrong...
> >> > After enabling the console logging, some time it takes days or weeks
> to
> >> see
> >> > the failure again...
> >> >
> >> > Thanks in advance,
> >> > Christian
> >> >
> >> > --
> >>
> >>
> >>
> >> --
> >> --
> >> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
> >>
> >
> >
> >
> > --
>
>
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
>


--

--20cf300fafe51c69ac04cd4eeb46--