BuildMaster Documentation

Integrating Azure DevOps with BuildMaster

  • Last Modified: 2020-02-25

Azure DevOps is a CI/CD service provided as part of Microsoft's Azure platform. Their pipelines support containers natively, so many shops building and deploying containers turn to Azure DevOps Pipelines.

BuildMaster is designed to work alongside Azure DevOps to provide a self-managed CI/CD solution. BuildMaster's Azure DevOps integration supports the following functionality:

Installing the Azure DevOps Extension

Simply navigate to the Admin > Extensions page in your instance of BuildMaster and click on the Azure DevOps extension to install it.

If your instance doesn't have Internet access, you can manually install the Azure DevOps extension after downloading the Azure DevOps Extension Package.

Connecting to Azure DevOps Using Resource Credentials

An Azure DevOps Resource Credential is used to connect BuildMaster to Azure DevOps at the instance level, but also supports connections on a "team project collection" level. These credentials are effectively a username and personal access token, so we recommend creating a specific account with the minimum amount of privileges required to interact with Azure DevOps, typically the permissions to the projects that will be integrated with BuildMaster.

To connect to a standalone instance of Azure DevOps (i.e., Azure DevOps Server), make sure the instance URL of the resource credentials is configured to the hostname for your installation, for example: https://azure-server.apps.corp

Resource credentials can be defined at the system-level or the application-level, and they can inherit from one another, such that configuring the "parent" resource credential will automatically give that configuration to its "child" credentials. This allows you to define some fields (such as name/password) at the system level, while defining repository-specific information at the application level.

More on this topic:

Is this documentation incorrect or incomplete? Help us by contributing!

This documentation is licensed under CC-BY-SA-4.0 and stored in GitHub.

Generated from commit 99e6640e on master