| Table of Contents | ||||
|---|---|---|---|---|
|
Creating an Azure DevOps Tool in Opsera
Login to the opsera portal
Navigate to Tool Registry
Click +New Tool
In the Create New Tool form, enter a Tool Name, select Azure DevOps as the Tool Identifier and fill out any other additional fields.
...
The next steps will show you how to create a personal access token in the Azure portal. This personal access token will then be used to Configure your Azure DevOps tool.
Configuring your Azure DevOps tool
Create a personal access token in the Azure DevOps portal
In your Azure DevOps portal, select the User Settings icon, located on the upper right hand side of the screen.
...
2. Select Personal access tokens from the dropdown
...
3. Fill out the required fields and make sure to select “Full access” in Scopes.
...
4. Copy the personal access token provided in the next step. Warning: It is not stored and you will not be able to see it again.
...
Configuring your Azure DevOps Tool in the Opsera Portal
In the Opsera portal under Tool Registry, open your Azure DevOps tool.
Navigate to the Connections tab.
Provide values for the following fields:
Personal Access Token - Paste the Personal Access Token retrieved in the instructions above.
Organization - Provide the DevOps organization set by the user in the azure DevOps portal. It must match the name used in the portal exactly.
Your tool can now be used in your Azure DevOps pipeline.
Setting up an Azure DevOps Pipeline in Opsera
Create a new Azure pipeline in the Opsera portal
In Pipelines, click +New Pipeline
Locate the Blank Pipeline Template and click Create Pipeline
In the Workflow tab, edit the Un-Configured Step. Select Azure DevOps from the Tool dropdown and Save
...
Configure your Azure Pipeline in Opsera portal
In your pipeline step, click on the gear icon to Configure Step Settings
2. In the Step Configuration, you are simply inserting the proper values of a pipeline which has already been configured in the Azure DevOps portal.
3. Configuration Settings
...
a. Azure DevOps Tool - This will auto populate with Azure DevOps tools saved in your Tool Registry. If you need to edit or reconfigure the tool, click View Or Edit this Tool’s Registry settings.
b. Organization Name - This is located within your Azure DevOps portal.
...
c. Project Name/ID - If you signed up for Azure DevOps with an existing MSA or GitHub identity, you're automatically prompted to create a Project. Find this in the Azure portal in your organization name under Projects. The Pipeline IDs from your Azure DevOps portal will then be automatically populated in Pipeline ID for you to choose from.
d. Pipeline ID - This will automatically be populated upon entering your Project Name/ID.
...
e. Pipeline Version - You can have several versions of the same pipeline in Azure. For example you can have versions 1, 2, and 3 for dev, test, and production. If this field is unspecified, it will default to the most recent version.