Inject same env variables when building container and exec command #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi
Like it said in https://issues.jenkins-ci.org/browse/JENKINS-32393, the injection of environment variables like JAVA_HOME or PATH in the container making trouble, and are not IMO in the feeling of the container way.
Moreover, I see that you have still changed this when the container start here : 79e47f5
I think this is the same when executing each command.
This PR do that.
But maybe you will think that add get/set in BuiltInContainer.java is not the right way to do that, so it's the "facility way", I can change this if you have a better implementation in mind (I'm pretty sure of that).