You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Matt Sicker <bo...@gmail.com> on 2022/01/28 16:31:34 UTC
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 a few threads before about having redundant PR checks, so I’ve gone ahead and disabled the Jenkins checks at least.
—
Matt Sicker
Re: I've disabled the Log4j2 Jenkins build for now
Posted by Gary Gregory <ga...@gmail.com>.
Thanks Matt!
Gary
On Fri, Jan 28, 2022, 11:31 Matt Sicker <bo...@gmail.com> 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
>
>
Re: I've disabled the Log4j2 Jenkins build for now
Posted by Matt Sicker <bo...@gmail.com>.
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ı <vo...@yazi.ci> 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 <bo...@gmail.com> 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
>>
>>
Re: I've disabled the Log4j2 Jenkins build for now
Posted by Volkan Yazıcı <vo...@yazi.ci>.
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 <bo...@gmail.com> 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
>
>