recently we discovered that the Deploy a Package Octopus deployment step does not show an error in the logs if a transformation fails due to missing files. We only managed to find the error message in the verbose logs. Is it possible somehow to show these issues as actual errors? We would like to stop the deployment next time this happens (or at least get a warning).
I have set the variables below:
Unfortunately, those variables won’t work as the no match found is informational rather than a warning or error.
However, you could enable custom deployment scripts for this step. Then add some basic Powershell to check that the required file exists as a Pre-Deploy script and trigger a failure state if it doesn’t.
