Connect to Azure DevOps Git from Control Room

You can connect to Azure DevOps Git through the Control Room to check in and manage a bot and its dependent files to the remote Azure DevOps Git repository. It creates a back-up for all your checked-in bot and its dependent files on Azure DevOps.

Prerequisites

  • To connect to Azure DevOps Git from Control Room, ensure that you have the AAE_Admin role.
  • Ensure that you have an Azure DevOps account.
Note: Automation 360 supports custom role creation by allowing all permissions to be non-default and editable. However, for releases before version v30, system-created roles such as, AAE_Admin are mandatory. For more information, see System-created roles.

Procedure

  1. Log in to the Azure DevOps account.
  2. Create an Azure DevOps project. Provide a project name and description, select project visibility (public or private), and then click Create.
  3. Click Repos.
  4. Click Generate Git Credentials.
    Enter the username and the password or token. When you obtain a token to connect to Git, ensure that you have the Read and Write permissions in the Code section.
  5. Log in to Control Room as an administrator.
  6. Navigate to Administration > Settings > Remote Git repository integration and click Edit.
  7. Copy the Git repository path without any changes to HTTPS repository path (including username).
    For example, https://johnsmith@dev.azure.com/johnsmith/_git/johnsmith.
  8. Ensure you update Branch name, Password/Token and Confirm password/token fields.
    Note: The maximum number of password or token length supported in Control Room is 75 characters. However, Microsoft supports more secured token or password length of 84 characters. If you want to enable your Control Room to work with token or password length of 84 characters, see Unable to update the Password/Token field for Azure DevOps GIT Repository Integration (A-People login required).

    For the existing Remote Git repository integrations, password or token length of 52 characters will work until the existing password is expired.

  9. Click Connect and Save.
    To confirm whether your connection is successful, check in a file from the private repository to a public repository and verify that your changes are pushed to Azure DevOps Git repository.