I already looked at the code of the plugin.

But I don't think it will help in my case because I think it is related to
the *specific* way PATH variable is handled during shell scripts.
Cause when I explicitely override PATH values, it isn't taken into account.

This is maybe my fault (I don't override PATH in the good place), but I
didn't see anything in EnvInject being able to help me (I didn't spent
hours on its code either)

Frédéric Camblor  <http://fcamblor.wordpress.com/>
<http://www.twitter.com/fcamblor>
Bordeaux JUG <http://bordeauxjug.org/> Leader
Jenkins <http://jenkins-ci.org/> community member & plugin commiter



On Wed, Jul 31, 2013 at 12:37 AM, Marc MacIntyre <marc...@purestorage.com>wrote:

> envinject plugin will probably solve this for you:
>
> https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin
>
>
> On Tue, Jul 30, 2013 at 3:07 PM, Frédéric Camblor <fcamb...@gmail.com>wrote:
>
>> Hi everyone,
>>
>> I'm lacking in Jenkins API knowledge to be able to provide a specific
>> directory to the PATH variable during a job execution only.
>>
>> My need : I'm enhancing the NodeJS plugin with NodeJS & npm
>> auto-installers.
>> Once installed, node has a bin/ directory with potentially lots of
>> executables inside it (when a new npm package is installed, it might add
>> new executable to this bin/ folder).
>>
>> I'd like to provide some build step allowing to add NodeJS installation's
>> bin/ folder to the PATH variable, during a specific build execution.
>> It could then make it possible to call some npm executables during shell
>> executed scripts (such as grunt, bower, jasmine and so on...)
>>
>> I tried appending launcher.env("PATH=/path/to/node/bin:<existing PATH
>> value>"), but it didn't seemed to work (executable not found).
>>
>> If you have any input/doc to help me, I take it ! :-)
>>
>> Thanks in advance,
>>
>> Frédéric Camblor  <http://fcamblor.wordpress.com/> 
>> <http://www.twitter.com/fcamblor>
>> Bordeaux JUG <http://bordeauxjug.org/> Leader
>> Jenkins <http://jenkins-ci.org/> community member & plugin commiter
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
>
> --
> Marc MacIntyre
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to