VSTS & DLM Automation Releases

jespana

Hi all,

We are evaluating RedGate's Source Countrol and DLM Automation tools for a CI/CD proof of concept project. With that said, is it possible to release to a local database (on-premise) from VSTS using DLM Automation? If so, what permissions need to be set to allow this to occur? And how does VSTS have to be setup to recognize an on-premise server?

Right now my release complains that the server can not be found.

2017-10-18T19:19:59.6237188Z ##[error]System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Couldn't connect to the database specified by the InputObject parameter: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Any feedback or guidance would be appreciated.

Thanks,
JEspana

PeterG

Hi,

DLM Automation just uses standard connections, the issue is likely to be in your network setup rather than the SQL Server permission.

To handle connections from VSTS you will need to do one of the following:

Running on VSTS hosted agents
- Ensure you can connect to those servers from a remote agent living in Microsoft Azure. You will need to fully qualify the server you are connecting to, and ensure the firewall is set up to allow these communications.

Running on local VSTS agents
- Ensure you can connect to the server from the machine running the VSTS agent.

For more information on local vs hosted see https://docs.microsoft.com/en-us/vsts/build-release/concepts/agents/agents

jespana

Hi Peter,

Thank you for the response and for the guidance. It has been extremely helpful.

way0utwest

I do this regularly and it works great. If you need help or more information, please ask. This all comes down to the VSTS agent acting as the client that deploys. Or you having a task that has the required credentials for the VSTS agent to make a connection.