The Context
I have an on-prem TFS (Azure DevOps) server (version 2018.2) with a single deployment agent installed.
This agent is in a shared deployment group and is used to deploy multiple IIS web applications, each application residing in its own project and release pipeline.
The release pipelines all use an identical flow, running the IIS Web App Deployment module to deploy each application.
In the deployment parameters each application has its own, unique virtual application
specified.
The Problem
When one application is deployed, it correctly deploys to its unique virtual application, but all other virtual applications that the agent is configured to deploy even in other release pipelines get overwritten by the one application.
What I have tried
- Verified that each
virtual application
parameter is, in fact, unique in the configs - Verified that the release deployment logs for any given deployment do not mention any extra deployment paths. This is particularly perplexing, because the logs say that the operation correctly deploys to only one virtual application.
- Check for any strange IIS logs on the target server
The Question
What are the best next steps for debugging an Azure DevOps issue like this? This is an on-prem server, so I have a higher level of access than if this were cloud hosted.
I am thinking perhaps:
- Check the agent version and update it to latest?
- Could there be other logs with valuable info? On the target server? On the DevOps server?