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ı <[email protected]> wrote: > > Thanks so much Matt! > I have created LOG4J2-3376 > <https://issues.apache.org/jira/browse/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 <[email protected]> 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 the master and release-2.x branches. I believe we’ve talked about >> this in a few threads before about having redundant PR checks, so I’ve gone >> ahead and disabled the Jenkins checks at least. >> — >> Matt Sicker >> >>
