microsoft/azure-pipelines-tasks

Tasks for Azure Pipelines

Owned by Microsoft

View on GitHub ↗Jump to charts ↓

microsoft/azure-pipelines-tasks has 3.5k+ stars and 2.5k+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 19th, 2026
Created on December 6th, 2014
Open Issues & Pull Requests: 416 (+0)
GitHub issues: Enabled
Number of forks: 2,694
Total Stargazers: 3,660 (+0)
Total Subscribers: 260 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.3 days
Mean response time: 51.4 days
90th percentile: 180.7 days
Tracked items: 1,015

Maintainer activity

30 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "regression" is answered fastest, typically in about 12 hours, while "route" waits about 9 days. 62% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 49% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 205
New in 7 days: 2
Closed in 7 days: 2
Avg open age: 624 days
Stale 30+ days: 164
Stale 90+ days: 100

Recent activity

Opened in 7 days: 2
Closed in 7 days: 2
Comments in 7 days: 4
Events in 7 days: 7

Top labels

  • triage (807)
  • bug (692)
  • stale (600)
  • Area: Release (505)
  • enhancement (231)
  • Area: ABTT (226)
  • help wanted (108)
  • Area: Artifacts (87)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Azure Pipelines Tasks is a collection of task modules that provide out-of-the-box functionality for Azure Pipelines and Team Foundation Server build and release workflows.

The repository addresses the need to execute common build and deployment operations within pipeline definitions. Tasks function as tool runners that encapsulate knowledge about how to invoke tools like MSBuild and VSTest, handle return codes, manage standard output and error streams, write timeline records based on expected output, and access credentials for writing back to Azure Pipelines or TFS. The project serves as both a production library of tasks and a reference implementation showing how to write custom tasks for deeper tool integration or reusability across many pipeline definitions.

Developers should use these tasks when they need first-class integration with common build tools and platforms within Azure Pipelines. The repository is most suitable for teams running continuous integration and deployment workflows on Azure Pipelines or Team Foundation Server. For custom functionality, the README notes that using existing script-running tasks such as PowerShell or Bash is often simpler than writing new tasks, and recommends writing new tasks primarily when deeper integration or broad reusability across many build definitions is required. Custom tasks can be uploaded to Azure Pipelines using the TFS Cross Platform Command Line utility or deployed within an Azure DevOps extension.

The project maintains active build and test coverage across Windows, macOS, and Linux platforms. The repository accepts contributions and has established a deprecation process for tasks that are no longer actively maintained, with deprecated tasks displaying warning banners in pipelines and being removed after a notice period. A deprecation file documents which tasks are no longer supported and provides migration guidance to replacement tasks.