Broken Build Manager

An Azure DevOps extension that surfaces failed pipeline builds across your project and lets your team assign ownership directly from within Azure DevOps — no spreadsheets, no Slack threads.

What it does

The extension adds a Broken Builds hub to the Azure Pipelines section of your Azure DevOps project. From there you can:

• See every broken pipeline at a glance — only the most recent failed build per pipeline is shown, and pipelines that have since gone green are automatically removed from the list
• Assign a build to a team member — use the Azure DevOps people picker to find and assign any user in your organisation
• Unassign a build — remove an assignment when it is no longer needed
• Filter to your assignments — toggle "My assignments" to see only the builds assigned to you
• Click through to the build — the build number links directly to the Azure DevOps build results page

Each row in the table shows:

Benefits

Visibility

Failed builds are often discovered late — after another developer is blocked, or after a customer reports an issue. The extension puts every broken pipeline in one place, visible to the whole team without needing to check each pipeline individually.

Accountability

Assigning a build to a specific person makes it clear who is responsible for the fix. The assignee receives an email notification the moment they are assigned, so nothing falls through the cracks.

Context

Each row shows the branch, the person who triggered the build, and how long ago it failed — giving the assignee everything they need to start investigating without leaving the page.

Noise reduction

Pipelines that have already recovered (latest run is green or partially succeeded) are automatically hidden. Only pipelines that are genuinely still broken are surfaced.

Traceability

The assigned-by field and assignment timestamp are stored persistently using Azure DevOps extension storage, giving a lightweight audit trail of who took ownership and when.

How it works

The extension is built with React and the Azure DevOps Extension SDK. Assignment data is stored directly in Azure DevOps extension storage — no external database, no connection strings, no secrets.

Email notifications are sent via an Azure Functions API backed by Azure Communication Services, using a verified custom domain (timelogextension.com).