Re: Autoinstaller plugin providing directory to the PATH
Hello, Probably, you could use Custom Tools Pluginhttps://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 Pluginhttps://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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Autoinstaller plugin providing directory to the PATH
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 o.v.nenas...@gmail.comwrote: Hello, Probably, you could use Custom Tools Pluginhttps://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 Pluginhttps://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 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.
Re: Autoinstaller plugin providing directory to the PATH
Regarding Custom Tools Plugin, we should thank Ryan Campbell, because he is an author of available versions (0.1 and 0.2) of Custom Tools Plugin. BTW, I'm going to add many sweet features into the next versions :) Best regards, Oleg Nenashev RD Engineer, Synopsys Inc. www.synopsys.com четверг, 1 августа 2013 г., 11:29:04 UTC+4 пользователь Frédéric Camblor написал: 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 o.v.ne...@gmail.comjavascript: wrote: Hello, Probably, you could use Custom Tools Pluginhttps://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 Pluginhttps://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 jenkinsci-de...@googlegroups.com javascript:. 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.
Re: Autoinstaller plugin providing directory to the PATH
You override ToolInstallation.buildEnvVars() Its Javadoc explains how to add it, and see JDK.buildEnvVars() for a concrete example. On 07/30/2013 03:07 PM, Frédéric Camblor 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. -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins Enterprise, our professional version of Jenkins -- 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.
Re: Autoinstaller plugin providing directory to the PATH
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.comwrote: 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.comwrote: 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.
