You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.
@moylop260 That's because ssh creates a non-interactive shell thus i won't load those vars, in bash is possible to override this adding the variables (if you want them to available for all users) in /etc/profile so they'll be available for all users in both modes (non and interactive) or in the user's ~/.bashrc
As they are not secrets, I guess that there is no problem adding those files
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently we have ssh access for runbot builds but the environment variables is not detected
Using:
Many variables are used from MQT scripts could be a good feature have this environment variables.
NOTE: Except environment variables secrets like as TOKEN
The text was updated successfully, but these errors were encountered: