#Subversion browser code#

This is probably caused by a firewall blocking traffic from these servers. If the simple test pipeline mentioned in the above section fails with an error, then the Subversion server is probably not reachable from Microsoft-hosted agents.

Not reachable from Microsoft-hosted agents If this passes, then you can continue using Microsoft-hosted agents.

#Subversion browser code#

To check whether they can, create a simple pipeline to use Microsoft-hosted agents and make sure to add a step to check out source code from your server. This often comes down to whether Microsoft-hosted agents can reach your server. Reachable from Microsoft-hosted agentsĪ decision you have to make is whether to use Microsoft-hosted agents or self-hosted agents to run your pipelines. Furthermore, you need to have a public DNS entry for the Subversion server so that Azure Pipelines can resolve the FQDN of your server to an IP address. See the section on Azure DevOps IPs to see which IP addresses you need to allow. For example, you can add exceptions to your firewall rules to allow traffic from Azure Pipelines to flow through. If the Subversion server cannot be reached from Azure Pipelines, work with your IT department to open a network path between Azure Pipelines and your server. If there are, then Azure Pipelines will start a new run. In other words, Azure Pipelines periodically checks the Subversion server if there are any updates to code. To integrate with Subversion, create a Subversion service connection and use that to create a pipeline. Otherwise, you must set up self-hosted agents that can access your on-premises server and fetch the code. If your server is reachable from the hosted agents, then you can use the hosted agents to run manual, scheduled, or CI builds.

YAML pipelines do not work with Subversion repositories.