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 <[email protected]> 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 <[email protected]> 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 <[email protected]> > > > 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 <[email protected]> -- Matt Sicker <[email protected]>
