MavenInDocker: Does not work when pom is in subfolder about ces-build-lib

[schnatterer]

@sklein94 thanks for reporting.
I stumbled upon this issue before. Not with maven but with dir and docker.
My solution was to explicitly mount the whole Jenkins workspace into the container.

docker.image('someImg')
  .inside("-v ${env.WORKSPACE}:${env.WORKSPACE}") {
     //...
 }

We could apply this to MavenInDocker in general. Do you think this would solve your issue?

You can try it out in a replay. Just set the following

String runArgs = "-v ${env.WORKSPACE}:${env.WORKSPACE} "

Here:

ces-build-lib/src/com/cloudogu/ces/cesbuildlib/MavenInDockerBase.groovy

Lines 30 to 43 in 70ea143

	String createDockerRunArgs() {
	String runArgs = ""
	if (useLocalRepoFromJenkins) {
	// If Jenkin's local maven repo does not exist, make sure it is created by the user that runs the build.
	// Otherwise, if not existing, this folder is create as root, which denies permission to jenkins
	script.sh returnStatus: true, script: 'mkdir -p $HOME/.m2'
	// Mount Jenkin's local maven repo as local maven repo within the container
	runArgs += " -v ${script.env.HOME}/.m2:${script.pwd()}/.m2"
	}
	return runArgs
	}

[sklein94]

@schnatterer
Thank you for your response.
Yes, this sounds good and should solve my issue!