Configuration variables not expanded while persisted to global variables from event handlers

Hi Guys,

We’ve recently upgraded to 1.9.2.1185
Since then - when a build is persisting a global scope variable using a persist event handler and a variable in the “new value” field - the variable is NOT expanded when the persist operation occurs:

We’re using “update value” for persist and in “new value” we have a configuration variable
(this should set the global variable to use the same value as in the configuration variable)
“Expand variable references in new value” is of course - checked.
But the end result is: the Global Variable holds the string “%ConfigVariable%” (Without the double quotes) instead of holding the expanded value of that variable.

This behavior breaks some of our flows, we use global variables to set/unset some flags that affect all of our builds (we have an intricate set of global flags and configuration conditions that allow us global control over most of our configurations)

Could you kindly look into this?

Thanks for reporting this Arik, we’ve reproduced the issue and fixed it by adding back some lines of code which somehow got deleted. We’ll have a new version out soon.

1 Like

Fixed in v1.9.2.1199.

1 Like