pass information on Jenkins user to container launch script #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm flexible about the exact name of the environment variables. |
|
Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests. |
Some container launch scripts may need to know the username and user/group IDs of the Jenkins user which the actual build steps will run as. In particular the container launch script may want to provide a background service, such as a graphical environment, for use during the build. This change passes in this information as part of the container's process environment.
jcarrothers-sap
force-pushed
the
jenkinsUserInfo
branch
from
18bc4ff to
185d6eb
Compare
|
Is there anything I can do to move this PR along? This change has been working well in our internal Jenkins environment for nearly 2 years now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some container launch scripts may need to know the username and user/group IDs
of the Jenkins user which the actual build steps will run as. In particular
the container launch script may want to provide a background service, such as
a graphical environment, for use during the build.
This change passes in this information as part of the container's process
environment.