Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
USER env var does not always exist #367
Comments
ryan-beisner
commented
Oct 31, 2017
|
ryan-beisner
commented
Oct 31, 2017
•
|
This has stopped the line in OpenStack Charms dev/test/release automation. We can add glue to export a USER env var if necessary, but wanted to raise this here as it may break other people too. Please advise. |
ryan-beisner
commented
Oct 31, 2017
|
A work-around for us would require modification of 30+ tox.ini files to ensure USER env var is passed to virtualenvs. |
added a commit
that referenced
this issue
Oct 31, 2017
johnsca
referenced this issue
Oct 31, 2017
Merged
Don't rely on any env vars to determine $HOME #368
added a commit
that referenced
this issue
Oct 31, 2017
johnsca
closed this
in
#368
Oct 31, 2017
added a commit
that referenced
this issue
Oct 31, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ryan-beisner commentedOct 31, 2017
The latest stable release of charm tools causes the tool to fail when run by non-human users such as jenkins, where the USER env var is not defined.
See https://bugs.launchpad.net/charm-test-infra/+bug/1728680
This is where the issue was introduced: #349