Does bamboo cache its global variables?

[Jeff MacDonald]

Hi,

I'm using a global variable in a deployment project. Its a password that I recently had to change. The deployment tasks still uses the old one. I checked in the database table called variable_definition and have confirmed that the DB holds my new valid password.

I've started and stopped the bamboo process wondering if it was a cache somewhere...

Suggestions??

[Przemek Bruski · Accepted solution]

Does it happen for new builds or just old builds that you rerun?

[Jeff MacDonald]

It happens when I try to run deploymet projects on old build results yes. If i create a new build results it will use the new variable-data. Didn't expect that behavior. All is well now.

[Jeff MacDonald]

It happens when I try to run deploymet projects on old build results yes. If i create a new build results it will use the new variable-data. Didn't expect that behavior. All is well now.

[Przemek Bruski]

Yeah, Bamboo snapshots the variable state so that you get consistent build reruns

[Marcin Sidorczuk]

is there is a way to force using current global variables instead of variables from snapshot? We are using global variables for storing servers list for deployment, now if we deploy some older build it is deployed only to part of servers.

[Przemek Bruski]

No, no way. But you can run a custom build against the same revision. It will get the current variables.

[Gabriel Ribeiro]

A suggestion ticket has been created covering this request:

• Global variables should be read at runtime during deployment 

Thank you.

best,
Gabriel Ribeiro

[PhilipJ]

Thanks Gabriel.

I've voted for the issue.