*String value = "Hello env vars";
build.addAction(new hudson.model.ParametersAction(new
hudson.model.StringParameterValue("VAR_NAME", value));*
variable VAR_NAME will be available by next build steps via standard
variable tag $VAR_NAME
On Tuesday, October 30, 2012 5:44:06 PM UTC+2, Michael Hüttermann wrote:
>
> an environment variable such as WORKSPACE.
> actually it does not matter how to solve the task, which is to pass a
> variable from the Builder#perform to a different Builder that is executed
> later as another build step, in the same Jenkins build job.
>
>
> On Tuesday, October 30, 2012 4:30:17 PM UTC+1, HX_unbanned wrote:
>>
>> What kind of env vriables you are reffering to?
>>
>> Nodes ?
>>
>> Slave/Master?
>>
>> System ( User / Machine / System context )?
>>
>> Build env variables, defined with build-scripts?
>>
>> For some part of the fun you can check out my battle against env variable
>> mess in Jenkins that I find inacceptable in any production software ..
>>
>>
>> http://stackoverflow.com/questions/12670572/passing-system-env-variable-into-jenkins-slave
>>
>> 2012/10/30 Michael Hüttermann <[email protected]>
>>
>>> thanks, but this solution has the indirection via another plugin. How
>>> can I directly set environment variables in the Jenkins plugin?
>>>
>>>
>>> Michael
>>>
>>>
>>>
>>>
>>> On Tuesday, October 30, 2012 2:40:06 PM UTC+1, xterm wrote:
>>>>
>>>> Geez, sorry was in a hurry
>>>>
>>>> echo HG_CHANGESET=${HG_CHANGESET} > /tmp/workspace/hgchangeset.**
>>>> properties
>>>>
>>>> where the variable ${HG_CHANGESET} contains the 123:abcdefghi value.
>>>>
>>>> xterm
>>>>
>>>> On Tuesday, October 30, 2012 8:10:38 AM UTC-5, Michael Hüttermann wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> could you please give me a pointer what the recommended way is to set
>>>>> environment variables in hudson.tasks.Builder#perform, which are in
>>>>> turn
>>>>> read in a later build step inside the same job?
>>>>>
>>>>>
>>>>> Thank you.
>>>>>
>>>>>
>>>>> Cheers
>>>>> Michael
>>>>>
>>>>
>>
>>
>> --
>> A.C. Linards L.
>>
>
