I have come across a defect.
With a package that is using build metadata in it’s versioning, e.g v1.0.0+develop and then using the Deploy to IIS step, it results in the ‘+’ being mangled in the file path.
- Create a package with the version format of x.y.z-a+b (2.20.0-e403da7f.997+team-limpopo in my case)
- Create a deployment process with the IIS Deployment step in it
- In that deployment step, set it to deploy the package from step 1
- Run the deployment
Result is the path is mangled at the end, eg:
This causes weird IIS behaviour
Using Octopus v2018.2.0