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 2020/05/10 19:50:38 UTC

Re: [CI][FAILURE] log4j/release-2.x#37 has potential issues

We've identified and filed
https://issues.apache.org/jira/browse/LOG4J2-2839 as the root cause
here. Release commits don't have any value in being built in CI let
alone attempted to be deployed to the snapshots repository!

On Sun, 10 May 2020 at 14:22, Mr. Jenkins <je...@builds.apache.org> wrote:
>
>
> There is a build failure in log4j/release-2.x.
>
> Build: https://builds.apache.org/job/log4j/job/release-2.x/37/
> Logs: https://builds.apache.org/job/log4j/job/release-2.x/37/console
> Test results: https://builds.apache.org/job/log4j/job/release-2.x/37/testReport/
> Changes: https://builds.apache.org/job/log4j/job/release-2.x/37/changes
>
> --
> Mr. Jenkins
> Director of Continuous Integration



-- 
Matt Sicker <bo...@gmail.com>