Re: I've disabled the Log4j2 Jenkins build for now

Yes, that would be ok. If we ever need to add a Jenkins build again for something, we can find the files in the history. — Matt Sicker > On Jan 30, 2022, at 13:56, Volkan Yazıcı wrote: > > Thanks so much Matt! > I have created LOG4J2-3376 > to

Re: I've disabled the Log4j2 Jenkins build for now

Thanks so much Matt! I have created LOG4J2-3376 to track this story. Is it safe to delete files matching with the `*jenkins*` pattern in both `release-2.x` and `master`? On Fri, Jan 28, 2022 at 5:31 PM Matt Sicker wrote: > I’ve disabled the Je

Re: I've disabled the Log4j2 Jenkins build for now

Thanks Matt! Gary On Fri, Jan 28, 2022, 11:31 Matt Sicker wrote: > I’ve disabled the Jenkins build for Log4j2 as we’re already testing PRs > via GitHub right now. Unless we can use a GitHub Action to publish > snapshots, though, I’ll have to update our Jenkins build to simply do just > that for

I've disabled the Log4j2 Jenkins build for now

I’ve disabled the Jenkins build for Log4j2 as we’re already testing PRs via GitHub right now. Unless we can use a GitHub Action to publish snapshots, though, I’ll have to update our Jenkins build to simply do just that for the master and release-2.x branches. I believe we’ve talked about this in