-
New Feature
-
Resolution: Unresolved
-
Major
-
None
If our understanding is correct,
the following output from our Jenkins build,
running on SSH Slave and Docker cloud,
reveals that Maven extensions under /lib/ext folder are not considered
Established TCP socket on 43567
Copied maven35-agent.jar
Copied maven35-interceptor.jar
Copied maven3-interceptor-commons.jar
[projectname] $ /opt/JAVA_HOME_DEFAULT/bin/java -XX:+TieredCompilation -XX:TieredStopAtLevel=1 -Daether.syncContext.named.factory=file-lock -Daether.syncContext.named.nameMapper=file-gav -Djava.awt.headless=true -cp /home/jenkins/maven35-agent.jar:/opt/MAVEN_HOME/boot/plexus-classworlds-2.6.0.jar:/opt/MAVEN_HOME/conf/logging jenkins.maven3.agent.Maven35Main /opt/MAVEN_HOME /home/jenkins/remoting.jar /home/jenkins/maven35-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 43567
<===[JENKINS REMOTING CAPACITY]===>���channel started
Executing Maven: -B -f /home/jenkins/workspace/.../pom.xml clean install -Dmaven.logging=byproject --builder smart -T 1C
...
...
...
Using the MultiThreadedBuilder implementation with a thread count of ...
This felt similar to Maven non-interactive mode (batch) prevent's project extensions loading
However, we have proven that the relevant Docker image is equipped with the Maven extensions,
by running a Docker container from it and the relevant Maven commands successfully, with the SmartBuilder and Multithreaded Build Logging extensions being used and either with or without interactive mode enabled.
Using the SmartBuilder implementation with a thread count of ...
However, when we run the same through a Jenkins job of Maven nature,
Maven falls back to standard mode:
Using the MultiThreadedBuilder implementation with a thread count of ...
Use of Maven extensions file didn't work either.
Consequently, we cannot take full advantage of Maven parallel builds.
This is most certainly related to a Maven Integration Plugin behavior.
