Loading...

This issue is archived. You can view it, but you can't modify it. Learn more

XML

Word

Printable

The docker-pipeline changed its behavior with version 1.14 and is no longer allowing plugins to contribute the "PATH" environment variable.

The Pipeline Maven Plugin contributes to the PATH environment variable to specify the "mvn" command line arguments such as the settings file.

Due to this change of behavior, the Pipeline Maven Plugin is no longer able to inject specify Maven settings file.

If you need to specify the Maven settings file in a dockerized build agent using the Docker Pipeline Plugin,

continue to use the Docker Pipeline Plugin 1.13
or specify the maven settings files using the Config File Provider Plugin
or use pipeline-maven:3.0.3-beta-2 adapting the "PATH" environment variable or using Takari's Maven wrapper as described on the release notes

is duplicated by

JENKINS-47805 withMaven doesn't copy settings.xml to Docker container

JENKINS-47804 Setting "mavenLocalRepo" to ".repository" creates a "$WORKSPACE/?/.m2/repository" folder

is related to

JENKINS-48050 Replace Declarative Docker agent directive with new implementation

JENKINS-48284 pipeline-maven 3.0.3 update issues with certain maven plugins.

JENKINS-40484 Unable to use withMaven() step inside docker container for old versions of Docker