-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 2.36, Pipeline Maven Plugin 0.4
I'm not able to use withMaven step inside docker container.
[Pipeline] withMaven
$ docker exec ffff env printenv MAVEN_HOME
$ docker exec ffff env printenv M2_HOME
$ docker exec ffff env /bin/sh -c "which mvn"
Using maven exec: /opt/apache-maven-3.3.9/bin/mvn
Using global settings config with name MavenGlobal
Replacing all maven server entries not found in credentials list is false
[Pipeline] {
[Pipeline] sh
[test-XXX] Running shell script
nohup: failed to run command `sh': No such file or directory
[Pipeline] }
[Pipeline] // withMaven
My Jenkinsfile pipeline:
node('docker') {
stage('Checkout') {
checkout scm
}
buildInDocker('linux') {
stage('Maven') {
withMaven(globalMavenSettingsConfig: '11111111-2222-3333-4444-555555555555') {
sh 'mvn clean test'
}
}
}
}
It looks like PATH env gets overwritten.
- is related to
-
JENKINS-41339 Environment variables referencing other variables broken
-
- Reopened
-
-
JENKINS-47823 withMaven fails to inject Maven settings files with docker-pipeline 1.14
-
- Closed
-
-
JENKINS-47809 Docker container does not read maven settings.xml after updating
-
- Resolved
-
- relates to
-
JENKINS-41204 pipeline does not use docker environment
-
- Open
-
-
JENKINS-43590 docker.inside() breaks container environment.
-
- Open
-
-
JENKINS-48050
Replace Declarative Docker agent directive with new implementation
-
- In Progress
-
- links to
- mentioned in
-
Page Loading...