This document describes the detailed steps to integrate Azure DevOps for Version Control System in Denodo. Currently, the Denodo Platform supports GIT, Subversion and Microsoft TFS for the Version Control System and GIT can be used to configure the connection to the Azure DevOps repository.
Version Control Systems helps managing workflows and changes to source code over time. In Denodo, VCS helps to manage the metadata of the Denodo elements involving developers working simultaneously on the same elements.
The VCS integration is supported in Denodo for both Virtual DataPort and the Solution Manager. In Virtual DataPort servers, it can be used for integrating the work done simultaneously by different members of the development team. In the Solution Manager, it can be used to save a backup file of the environments after deployment, both for successful and unsuccessful deployments.
Microsoft Azure DevOps provides version control, reporting, requirements management, project management, automated builds, testing and release management capabilities.
Azure DevOps integration provides repositories for an integrated and collaborative environment supporting continuous integration for managing workflows. The Denodo Platform integration with Azure DevOps helps managing and storing metadata in Azure repositories via VCS operations.
This section explains how to configure Azure DevOps for Version Control in Denodo Virtual DataPort.
The user must have an organization created in Azure DevOps and a project created. If you have not created an organization adn project, follow the steps in Create an organization or project collection and Create a project in Azure DevOps sections of the Azure DevOps documentation.
For instance: https://dev.azure.com/Denodo8
The Clone Repository window contains the URL for VCS configuration and the user authentication credentials. The URL has the following format:
For instance: https://Denodo8@dev.azure.com/Denodo8/Azure_Denodo8/_git/exercise_lab
The username and PAT token are necessary for configuring VCS on the Denodo side and can be obtained by clicking on the Generate Git Credentials option.
The Personal Access Token (PAT) is used as an alternate password to authenticate into Azure DevOps and is essential to connect to Azure DevOps from Denodo. This access token value needs to be specified in the password section of the Denodo VCS configuration window. As the PAT tokens are not stored, you can copy the token for future needs or generate a new PAT token.
NOTE: The VCS configuration can be done only by the administrator. Hence, it is necessary to log in to Virtual DataPort as administrator.
The Azure DevOps repository is now integrated with the Virtual DataPort server for VCS management.
To configure Azure DevOps for Version Control System in the Solution Manager, follow the initial steps for the Azure DevOps repository setup (create a new repo for SM) mentioned in the Configuring Azure Devops for VCS in Virtual DataPort section and then follow these steps:
To fill in configuration details under this section, open the Azure DevOps repository to be integrated for VCS setup in Solution Manager. Click on the Clone option which opens the Clone Repository window with the required details.
The Azure DevOps repository is now configured for the Solution Manager VCS. After this set up, change the environment configuration before a deployment so the Solution Manager stores a backup on the remote repository for every action of revision deployment to that environment.
NOTE: In these steps we have explained how to configure Azure DevOps using Personal Access Tokens (PATs). It is also possible to use SSH keys to configure the integration with Azure DevOps, see Virtual DataPort Server Configuration for more information.