You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Christian Müller <ch...@gmail.com> on 2012/10/30 08:11:15 UTC
Access log files on builds.apache.org
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
--
Re: Access log files on builds.apache.org
Posted by Christian Müller <ch...@gmail.com>.
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 <da...@gmail.com>wrote:
> 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 <ch...@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üller <ch...@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
>
--
Re: Access log files on builds.apache.org
Posted by David Karlsen <da...@gmail.com>.
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 <ch...@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 <da...@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üller <ch...@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
Re: Access log files on builds.apache.org
Posted by Christian Müller <ch...@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 <da...@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üller <ch...@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
>
--
Re: Access log files on builds.apache.org
Posted by David Karlsen <da...@gmail.com>.
You could configure the job to archive the log-files - then they
should appear under archived artifacts.
2012/10/30 Christian Müller <ch...@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