Thanks to both of you, I should achieve what I want with these hints/examples :-)
@Oleg Didn't knew of this two plugins which sound great ! Unfortunately, I already implemented everything in the NodeJS plugin which should make your Custom Tools Plugin example even easier by not having to write any line of code :-) ... but the initiative is cool to have a simple workaround to install something which hasn't any autoinstaller yet. Thanks again :) 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 Thu, Aug 1, 2013 at 8:30 AM, Oleg Nenashev <[email protected]>wrote: > Hello, > > Probably, you could use "Custom Tools > Plugin<https://wiki.jenkins-ci.org/display/JENKINS/Custom+Tools+Plugin>". > Via this plugin you can specify your own tools and installers. Version 0.3 > will add support of the variables and label-specific installation options. > > If you need to specify path w/o any installation steps, you can use Extra > Tool Installers > Plugin<https://wiki.jenkins-ci.org/display/JENKINS/Extra+Tool+Installers+Plugin> > > Best regards, > Oleg Nenashev > > среда, 31 июля 2013 г., 2:07:18 UTC+4 пользователь Frédéric Camblor > написал: > >> 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
