Unrecognised version of configuration during deployment

Hi there,

We are running BuildMaster version 3.5.6 build 22, self-hosted.

I have a configuration file - a log4net.config - that, during edit and when viewing under 'recent changes', is as expected.

However, as soon as I go to deploy the file - either during a workflow or using the 'Deploy Configuration File' functionality, the contents don't match what I'm expecting.

I believe I'm seeing an old version of the file. This is despite choosing a specific (the latest) version and irrespective of 'Force most recent template' yes/no.

Would appreciate any asistance in troublshooting this issue.

Regards,
Jonathan

Are you saying that when you deploy it manually that the "Deployed File Preview" window is showing something different than what is deployed?

If the text in the preview window matches what gets deployed, then make sure the release numbers to which the instance is saved matches or is newer than what is being deployed. Note the rule is that the newest configuration file version saved against a release less than or equal to the release being deployed is the one that is chosen.

If the preview window text does not match the file that is being deployed, some troubleshooting tips are:

ensure the selected server matches the one you're investigating
check the file's modified date to make sure it's actually being saved

Additionally, it's worth double-checking that the automated deployment plan doesn't overwrite the config file in a later action.

Hi,

Please ignore this question.

The issue was ultimately down to the config file having unescaped percentage symbols within it and hence variable substitution not working.

Regards,
Jay