You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2020/04/14 20:47:02 UTC
Re: Jenkins job log4j/master#47 failed
Matt,
Pipelines may be great but what are we supposed to do if you get hit by a truck? Once again I have no idea why the build is failing, how to figure it out, or even what to look at to try to figure it out.
If the build is going to work this way you really need to document how it works and what to look for if it fails in confluence.
Ralph
> On Apr 13, 2020, at 7:46 PM, Mr. Jenkins <je...@builds.apache.org> wrote:
>
>
> There is a build failure in log4j/master.
>
> Build: https://builds.apache.org/job/log4j/job/master/47/
> Logs: https://builds.apache.org/job/log4j/job/master/47/console
> Changes: https://builds.apache.org/job/log4j/job/master/47/changes
>
> --
> Mr. Jenkins
> Director of Continuous Integration
Re: Jenkins job log4j/master#47 failed
Posted by Matt Sicker <bo...@gmail.com>.
Turns out the error was because I had added -Djenkins to the windows
build which was only meant for the linux build apparently. That system
property activates a maven property for locating jconsole.jar looks
like. That's a fragile build area (e.g., that same module doesn't
compile in Java 9+).
On Tue, 14 Apr 2020 at 16:41, Matt Sicker <bo...@gmail.com> wrote:
>
> This is supposed to be working. Let me retry the build. The previous
> errors were sometimes related to timeouts due to too much build
> activity on builds.a.o.
>
> On Tue, 14 Apr 2020 at 15:47, Ralph Goers <ra...@dslextreme.com> wrote:
> >
> > Matt,
> >
> > Pipelines may be great but what are we supposed to do if you get hit by a truck? Once again I have no idea why the build is failing, how to figure it out, or even what to look at to try to figure it out.
> >
> > If the build is going to work this way you really need to document how it works and what to look for if it fails in confluence.
> >
> > Ralph
> >
> > > On Apr 13, 2020, at 7:46 PM, Mr. Jenkins <je...@builds.apache.org> wrote:
> > >
> > >
> > > There is a build failure in log4j/master.
> > >
> > > Build: https://builds.apache.org/job/log4j/job/master/47/
> > > Logs: https://builds.apache.org/job/log4j/job/master/47/console
> > > Changes: https://builds.apache.org/job/log4j/job/master/47/changes
> > >
> > > --
> > > Mr. Jenkins
> > > Director of Continuous Integration
> >
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
--
Matt Sicker <bo...@gmail.com>
Re: Jenkins job log4j/master#47 failed
Posted by Matt Sicker <bo...@gmail.com>.
This is supposed to be working. Let me retry the build. The previous
errors were sometimes related to timeouts due to too much build
activity on builds.a.o.
On Tue, 14 Apr 2020 at 15:47, Ralph Goers <ra...@dslextreme.com> wrote:
>
> Matt,
>
> Pipelines may be great but what are we supposed to do if you get hit by a truck? Once again I have no idea why the build is failing, how to figure it out, or even what to look at to try to figure it out.
>
> If the build is going to work this way you really need to document how it works and what to look for if it fails in confluence.
>
> Ralph
>
> > On Apr 13, 2020, at 7:46 PM, Mr. Jenkins <je...@builds.apache.org> wrote:
> >
> >
> > There is a build failure in log4j/master.
> >
> > Build: https://builds.apache.org/job/log4j/job/master/47/
> > Logs: https://builds.apache.org/job/log4j/job/master/47/console
> > Changes: https://builds.apache.org/job/log4j/job/master/47/changes
> >
> > --
> > Mr. Jenkins
> > Director of Continuous Integration
>
>
--
Matt Sicker <bo...@gmail.com>