There appears to be a rehash of an old bug.
We have been deploying a project for a couple of years. It runs through a variable substitution for web.config and it has been fine all that time.
This month though, we’ve been hitting this error.
System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.
Looking at the logs, this is because it is trying to convert jshint.config in the assets of a generally available JS library (DataTables). Nothing appears to have changed in the packaging process and this file has been available for years.
It’s not entirely clear why this has suddenly started failing when it was OK before. A tentacle upgrade was performed before this release went live. A second tentacle upgrade has since been performed and it’s still failing.
I note that this was a problem with Octopus 5 years ago with Octopus on-site (at the time people were asking for the ability to exclude files from variable substitution). Could be a red herring:
However, this appeared to be closed (https://github.com/OctopusDeploy/Issues/issues/1897) and of course, it has been fine up until the beginning of this month.
Anyone got any ideas? Setting variables to globally ignore warnings/errors isn’t ideal.