Updated, see build #15 for the latest failure.
On Sat, 11 Apr 2020 at 18:37, Matt Sicker wrote:
>
> Oh I see the issue here. Needs more back ports from master. I’ll update this.
>
> On Sat, Apr 11, 2020 at 18:25 Ralph Goers wrote:
>>
>> Why have these builds been failing for the last week? I loo
Now this looks to be a legit build failure from something recently merged.
On Sun, 12 Apr 2020 at 14:36, Mr. Jenkins wrote:
>
>
> There is a build failure in log4j/release-2.x.
>
> Build: https://builds.apache.org/job/log4j/job/release-2.x/15/
> Logs: https://builds.apache.org/job/log4j/job/relea
I've pushed the backport for fixing this build error. For those
curious: the problem was the "recordIssues" build step requires a
Jenkins agent to execute, and I had configured the pipeline not to use
on at the root level. The mail and slackSend steps are both node-less
steps (i.e., they're basical
I think I said this before, but I see no reason you can’t have a dependency on
Jackson. We currently do for almost all of our JSON processing. I wouldn’t
spend any more time trying to improve the performance of your custom support,
especially since - as I recall - you had to drop support of a fe
