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
When running a ruby script inside the deployment actions, RBENV_DIR is inherited from Samson's runtime in my deployment. That means anything expecting the right ruby to be set via .ruby-version will fail :(
While the fix is easy (unset RBENV_DIR at the beginning of the build), it needs to be done for every project separately and all teams need to learn about it. It would be great if I could configure Samson to drop some environment variables globally. For example never pass the RBENV_DIR / PATH / RAILS_ENV / HOME to the jobs it's running.
The text was updated successfully, but these errors were encountered:
I've run into an unexpected Samson behaviour.
When running a ruby script inside the deployment actions, RBENV_DIR is inherited from Samson's runtime in my deployment. That means anything expecting the right ruby to be set via
.ruby-version
will fail :(While the fix is easy (
unset RBENV_DIR
at the beginning of the build), it needs to be done for every project separately and all teams need to learn about it. It would be great if I could configure Samson to drop some environment variables globally. For example never pass theRBENV_DIR
/PATH
/RAILS_ENV
/HOME
to the jobs it's running.The text was updated successfully, but these errors were encountered: