[v3.4] Backport sudo -E CI fix#5187
Merged
m4dcoder merged 2 commits intoStackStorm:v3.4from Mar 11, 2021
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport of #5186
sudo -Eto preserve env varsGithub Actions has this in their Default: env_reset in their sudoers config file. This means that HOME and other vars are set to match the sudo target user. Using sudo -E preserves the environment allowing ~ to resolve correctly.
I'm not sure why we didn't hit this earlier. Maybe Github changed their sudoers config? In any case, this should fix it.