Previous warnings now fail deployment

We have just upgraded to Octopus 3, before this upgrade we always had some deployment warnings when doing config transformations that said: Unable to update the config file - it may not be a valid XML file: Reference to an undeclared entity ‘nbsp’.
It now appears that after the upgrade these warnings now fail the deployment.

I have tried adding Octopus.Action.Package.IgnoreConfigTranformationErrors with a value of True to the variables as per http://help.octopusdeploy.com/discussions/problems/23038-webreleaseconfig-transform-error
but this did not resolve the issue.
Apart from fixing up the files (Which is in the backlog) is there something else I can do.

Hi Myles,

Sorry about this. Could you give us an example of the file (or at least the parts that cause the errors) and we can add a test case for it? We should be able to ship a 3.0 patch pretty quickly with the fix.

Paul

Here you go Paul,

<?xml version="1.0"?>

The ’ ’ seems to cause the error. When I open it up in Visual Studio 2013, resharper also shows a squglly red line under this ‘’&nbsp’ too, yet it does not mind the ‘&gt’

just updated the comment to include more of the xml

Hi Myles,

Thanks very much! Here’s a bug report that you can monitor until it’s fixed:

Paul