You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2020/09/14 16:20:00 UTC

[jira] [Created] (LOG4J2-2920) Optimize various points of the build

Matt Sicker created LOG4J2-2920:
-----------------------------------

             Summary: Optimize various points of the build
                 Key: LOG4J2-2920
                 URL: https://issues.apache.org/jira/browse/LOG4J2-2920
             Project: Log4j 2
          Issue Type: Epic
          Components: Build
            Reporter: Matt Sicker


The current time it takes to perform a full {{mvn clean install}} (with dependencies already downloaded) as well as the time it takes to run {{mvn site}} has historically been a problem for making more frequent releases. Today, I see that even on a CI machine, the tests themselves take about 30 minutes to complete (unsure if this time includes the total wall time or only the time spent executing tests), half of that in log4j-core.

While working on LOG4J2-2653, I've begun the process of categorizing our tests and trying to identify which ones require special execution conditions (e.g., cannot be executed in parallel) with the hopes of enabling faster tests. With that idea in mind, I figured an actual epic for the various tasks required to optimize the build would make sense.

The goal of this epic is to update our Maven build so that tests can execute more quickly, less toolchains/compilers are required to build, and other friction points that add unnecessary time to the build.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)