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
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
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
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
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
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
