The Env Inject plugin lets you prepare an environment for the run where you can 
set environment variables but it is the first thing to happen so you wont have 
any files from current source control.

Without temporary files I don't think you can inject any environment variables 
after the source code is checked out.    We output the variable and value into 
a property file and then load it using Env Inject so subsequent build steps can 
take advantage of that environment variable.

Will

On 07/16/13 09:07, alan.martino...@gmail.com<mailto:alan.martino...@gmail.com> 
wrote:
Is it possible to set the Jenkins environmental variable within the build 
script?

I need this is because the log which the build script creates has to be sent to 
Gerrit via the Gerrit trigger plugin without the use of temporary files, so the 
only way I see it happening is via a Jenkins environmental variable.

--
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 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to