|
Hye, Same observation when building a maven project. The PATH expected and defined in the Dockerfile (through ENV command) is overwritten by the env ... PATH:... set in the docker exec command (Master configuration) => compilation failed with "java : not found" because PATH no more correct. Moreover, the PATH variable injected in the container is resolved on the Docker host and not in the container (ex: PATH=$ {JAVA_HOME}
/bin:$ {PATH}
) whereas injection could be correct if the JAVA_HOME was passed to the container in order to be resoled in it and not on the Docker host. Perhaps escaping the $ {...}
could be a solution..But it would be nice to have a parameter in the plugin to "Inject master env PATH and Tools" or not.
|