Question

Is it possible to define a new build parameter/ENV variable in a build step so it was available in the next one?

Let’s say I have 2 different “Execute shell” steps and want in the second step access the variable defined in the first one.

PS: the value for the variable is set in runtime – read from 3rd party resource, so I cannot harcode it, thus need to set it from the shell script.

Answer 1

The plugin EnvInject will do that for you.
It can be configured as pre-SCM step or as build steps. Put it in between your two existing build steps.

Update

In your case, it may be easier to just read the value of the “3rd party” file as part of your second build step:

var=$(<3rdpartyfile.txt)

After the above line, the contents of your 3rdpartyfile.txt will be available in environment variable var. You can now use $var as you would any other variable