Documentation

Looking for something in particular?

Configuring the Automation Secrets Password in Microsoft Azure Pipelines

Microsoft Azure Pipelines is a cloud service that you can use to automatically build and test your code project and make it available to other users. It works with just about any language or project type. We provided some instructions on how to set the Microsoft Azure Pipelines Secrets configuration.

Azure Pipelines combines continuous integration (CI) and continuous delivery (CD) to constantly and consistently test and build your code and ship it to any target.

This support article describes how to configure and encrypt the .secrets file when using a Continuous Integration (CI) tool such as Azure Pipelines to protect the security of your information. You can do this by defining the secret password within the Environment Variable

Instructions for Configuring Secrets within Azure Pipelines


Step 1: Configure Azure Pipelines using ANT. To get started, click Variables.

Step 2: Add a new variable, PROVARSECRET, and select lock to secure the credentials so that it is not displayed in plain text. 

Image showing how to add a new variable PROVARSECRET

Step 3: In the ANT task, provide the following command:

-Dsecrets.password=$(PROVARSECRET. This will replace the secrets.password property mentioned in the build.xml file with the encrypted password variable. 

Image showing a view of the ANT task with the secret password listed in Options

Above: View the ANT task with the secret password listed in Options.

Step 4: In the pipeline execution logs, you will see the secret password in encrypted form. These simple steps will help you in Microsoft Azure Pipelines secrets configuration.

In the pipeline execution logs, you will see successful Microsoft Azure Pipelines secrets configuration


Feedback

Was this article helpful for you?
Documentation library

Trying to raise a case with our support team?

We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.

Scroll to Top