Configuration Files not parsing variables after upgrade to v5

[William Graber]

We recently upgraded from Buildmaster v4.9 to v5.6. For the most part, the migration went off without any issue. However, I'm having problems with configuration files.

Previously, in the configuration file template, we could use built-in functions and variables and they would be interpolated on the deployment of configuration files.

For example, something like:

ApplicationDisplayName = $ApplicationName

When deployed, it would parse the variable and output something like:

ApplicationDisplayName = Example Application

As of v5.6, however, it doesn't get parsed at all, just outputing the raw text ($ApplicationName). Attempting to call any function results in a null output.

How can I get the configuration files to parse built-in variables again? We need to be able to put information from build runtime into configuration files.

Product: BuildMaster
Version: 5.6.11

[Alana]

Are you sure that you're on v5.6.11? There was a regression where that may have happened in v5.6.10

Also, make sure your settings (Application > Settings) are not to "old variables" only.

[C R Feamster]

Indeed. Version 5.6.11 (Build 2)

[Alana]

OK ; in this case, can you provide a simple reproduction case that we can try? Like, a new application that reproduces this? And please send this as a ticket -- Q&A are generally the lowest priority when it comes to support, so we want to handle it through better channels :)

The $ApplicatinName and $ReleaseNumber are standard test cases for us, so they do work in our config file replacement tests (which, are quite complex due to so many legacy cosniderations...)