Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-1472

Multibranch Pipeline supports JDK 7-10 Maven 3.2-3.5 Linux Windows



    • Task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.20.1
    • 2.21.0
    • None
    • None
    • ASF Jenkins CI


      Jenkinsfile exists but it fails on static code analysis.

      Performance problem with Publishers on Windows & Jenkins.

      Fixing build process and support multiple JDK Versions and platforms Linux/Windows.

      During the build when running with multiple versions of Maven (3.2.x - 3.5.x) and JDK versions (7 - 10) these problems were found and fixed in this Jira issue:

      1. maven-enforcer-plugin downloaded maven-surefire-api from Nexus which was previously built with Java 7.
        Therefore reordered modules (only surefire-api module before surefire-shadefire) in the aggregator POM.
      2. JUnit47ParallelIT reported
        Text not found in log: These tests are incomplete:
        because the JVM GC blocked the application.
        As a workaround is to fork the JVM and log everything to console:
        .redirectToFile( false )
      3. In ParallelComputerBuilderTest found a problem where the execution time was prolonged by calling System.gc() because Stopwatch includes the execution time spent in @Before
      4. Improved PC and PCB because this could cause hidden NPE. Added jvm.args.tests into argLine in order to lax GC.
      5. UmlautIT renames basedir directory to another directory with non-ASCII German word Umlaut. There the test threw IOException while renaming the directory of integration test because the directory could not be found on Windows 7 (Cp1250). The solution would be to create directories in the beginning of the test which is more safe than renaming the directory. Added maven-clean-plugin:3.0.0.
      6. Building the project with old Maven versions caused an error because classes from transient dependencies maven-shared-utils . This happened in the project maven-failsafe-plugin. After shading the artifacts and reduced the POM the maven-shade-plugin excluded maven-shared-utils.
      7. Unified the configuration of maven-surefire-plugin in the unit tests and configured the parameters: jvm, redirectTestOutputToFile, dependencies and added JUnit4SuiteTest.java as JUnit3 adapter.
      8. During the build process we could not identify directory of particular test configuration because one is overridden. Turned the Surefire1295AttributeJvmCrashesToTestsIT to Theories runner. Additionally it seems this IT is not stable because the SomeOtherTest.java has no delay which would be expected to take some time and simulate that the test set was interrupted in the middle. This IT interrupts the execution by calling native exit() etc.
      9. Renamed <artifactId>surefire-is</artifactId> to expected <artifactId>surefire-its</artifactId>.


        Issue Links



              tibordigana Tibor Digana
              tibordigana Tibor Digana
              0 Vote for this issue
              1 Start watching this issue