Skip to main content

Azure DevOps (Coming soon)

Azure DevOps support for code repositories is coming soon. This article explains what Pensero will read from Azure DevOps Services and Azure DevOps Server, and the access it will need.

Written by Wayne

Coming soon

Azure DevOps is not available to all organizations yet. To get early access, contact Pensero support.

Overview

Pensero will connect to your Azure DevOps Git repositories to understand what work is delivered and how much effort it takes to move it to production.

Pensero will support:

  • Azure DevOps Services (cloud, https://dev.azure.com/your-organization)

  • Azure DevOps Server (on-premises, https://your-server/your-collection). The server must be reachable from the internet over HTTPS.

Pensero supports Git repositories only. It does not read TFVC repositories, Azure Boards, Pipelines or Wiki.

What Pensero Will Read from Azure DevOps

From each Pull Request, Pensero will capture:

  • Title & Number

  • State (active, completed, abandoned, draft)

  • Description

  • Key timestamps (creation, approval, completion)

  • Author and reviewers, including reviewer votes

  • Comments and replies

  • Source & target branches

  • Diff metrics (lines changed, files changed)

Pensero will also read direct commits to the default branch, so trunk-based work is counted.

Access Pensero Will Need

Pensero will connect with a Personal Access Token (PAT). We recommend a PAT from a service account, because the token reads only what its user can see.

The PAT needs these scopes:

  • Code: Read

  • Project and Team: Read

The setup steps will be added to this article when Azure DevOps is available.

Did this answer your question?