I've used those steps for creating new environment variables in Jenkins,
but not for overwriting PATH, althouth you might use:
Value = $PATH:/adding/new/path/
in order not to lose previous value of PATH. Anyway, if scons is located in
/usr/local/bin (as you indicated), Jenkins would have to find it, because
that path is usually into PATH variable.
>From your output, I guess you're using SCons Plugin. Although it's not
necessary in this case, try to configure "SCons Executable Path" in "Global
/usr/local/bin (without /scons).
If problem persists, maybe it's a bug of SCons Plugin. Try to execute SCons
- Add build step > Execute shell
Tell us if you get it.
El miércoles, 12 de octubre de 2016, 18:29:50 (UTC+2), Uma escribió:
> Thanks for the reply
> Where can I set env variable for scons path?
> I have tried setting Jenkins -> Manage Jetkins -> configure System ->
> Global Properties -> Environment Variable :
> Name = PATH
> Value = /usr/local/bin/scons
> It does not seems to be work.
> On Wed, Oct 12, 2016 at 6:15 PM, Victor Martinez <victormar...@gmail.com
>> Apparently scons is not part of your env variable path.
>> Run 'which scons' and 'echo $PATH' then you will figure out what env
>> varianles were loaded when running that job.
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> To unsubscribe from this group and all its topics, send an email to
>> To view this discussion on the web visit
>> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.