Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Creating an OAuth Token for FlexDeploy ITS

  1. Go to Azure Boards and login as the user you want to comment on Azure Boards Issues with.

  2. Generate a Personal Access Token in Azure Boards following this guide: ​Personal access tokens | Azure Boards

  3. Choose an expiration date based on your security policies. Shorter expiration dates will require updating the ITS more frequently.

  4. Choose the following OAuth scopes to comment on and change status of issues:

Azure Boards ITS Instances

An Azure Boards instance looks like this:

Setting Up Folders and Projects to Use the Azure Boards ITS Instance

Then back in FlexDeploy, set up your folder ITS settings like this:

Azure Boards Issues only accept statuses of open and closed. Other statuses will be ignored.

Linking Azure Boards Issues to FlexDeploy Builds

Now you are ready to link tickets with commits or by manually entering them on project builds or project packages.

Linking with Commit Messages

Set up your FlexDeploy Project with a ticket pattern. The pattern must be Azure Boards repo name + “-” + issue number.

Following this pattern, make a commit message.

Push and merge your change.

When you create a build, the issue numbers are pulled from your commits.

Linking by Manual Entry at Project Build Time

If you didn’t remember to put the issue number in your commit, and you are building the project manually, you can enter issue numbers at build time.

The issue number should be Azure Boards Repo Name-Issue Number

In this example, it’s maven-project-3.

Linking Issues to Project Packages

If you don’t put issue numbers in your commits and you are working with a package-based project, you can associate issues with packages that will live through its build and deployment lifecycle by following this pattern.

Go to the project and package which you wish to link An Azure Boards Issue.

Edit the package.

Add one or more Issues. The dropdown only shows previously linked issues. Type the entire issue key to make a new one.

Save.

The issue number should be in the format Azure Boards Repo Name-Issue Number

Now, builds and deployments of this package will be associated to that Azure Boards Issue.

  • No labels