You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on adding Azure AD support to the Go language SQL server driver and a question that has come up in that project is how to do continuous integration for future pull requests.
I see this project has a continuous integration system set up for pull requests that runs in Azure DevOps - does it run against an Azure SQL server instance? Is it possible to authenticate using Azure AD and managed identities to support testing different authentication methods?
Please let me know if this is better handled as direct messages to the team - I realize this is not strictly on-topic for the JDBC driver, though you are definitely the closest thing I can find!
Hi @wrosenuance , azure-pipelines.yml will give you an idea. You should be able to run the CI both on custom and Azure hosted VMs/SQL Servers, assuming Azure Devops pipelines have access to the resources. More details can be found here .
It looks like an Azure Subscription is required - I'm guessing that means for this project that Microsoft manages / pays for the Azure Subscription used for CI? If so then we would need to find a way to fund / manage that for the Go driver project.
Question
I am working on adding Azure AD support to the Go language SQL server driver and a question that has come up in that project is how to do continuous integration for future pull requests.
I see this project has a continuous integration system set up for pull requests that runs in Azure DevOps - does it run against an Azure SQL server instance? Is it possible to authenticate using Azure AD and managed identities to support testing different authentication methods?
Please let me know if this is better handled as direct messages to the team - I realize this is not strictly on-topic for the JDBC driver, though you are definitely the closest thing I can find!
Relevant Issues and Pull Requests
denisenkom/go-mssqldb#547
The text was updated successfully, but these errors were encountered: