I noticed a problem when I updated this module.
Some paths are added, I guess with npm-run-path.
This is very intrusive as it add general paths and makes the command running with wrong processes.
In my case it takes a wrong version of ruby from /usr/bin rather than from an RVM folder.
Here are the added paths from the node process:
It is very intrusive to add /usr/bin as it takes precedence to my /var/lib/jenkins/.rvm/gems/ruby-2.4.1@global/bin, making the command run with the wrong version of ruby.
Having an option not to add these paths might be a good idea?
I noticed grunt-exec is not doing these kind of things.
I noticed a problem when I updated this module. Some paths are added, I guess with npm-run-path. This is very intrusive as it add general paths and makes the command running with wrong processes. In my case it takes a wrong version of ruby from
/usr/bin
rather than from an RVM folder. Here are the added paths from the node process:It is very intrusive to add
/usr/bin
as it takes precedence to my/var/lib/jenkins/.rvm/gems/ruby-2.4.1@global/bin
, making the command run with the wrong version of ruby.Having an option not to add these paths might be a good idea? I noticed grunt-exec is not doing these kind of things.
Any thoughts?