-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
jenkins 2.3, maven plugin 2.12.1, Custom build environment 1.6.5
When building a maven job inside a container with the custom build environment plugin, the maven plugin parses the POMs outside of the build environment container.
Because of this, I had to install and configure maven on my build host instances (and I fear I may have maven version issues because of that).
Ideally, the integration between the two plugins should be improved to :
- Skip checks that maven is configured as a global tool when the build is done in a container
- Perform all maven plugin operations (verify that the $MAVEN_HOME is valid, parse poms, etc...) inside the custom build environment container.
------------------------ BUILD LOG -----------
Started by user Manuel Ryan
Building remotely on 1b9e724c23c243 in workspace /home/jenkins/workspace/test-maven-project
...
Docker container 1e6bc6c66395543cfc391ac360096a06249cb72eb168496d6487e5165a346234 started to host the build
Parsing POMs <-- should be an "exec" inside started container
For anyone stumbling on this issue : My workaround was to switch to the Kubernetes plugin instead of the "custom-build-environment" plugin.