Analysis updated 2026-05-18
Look up how a built-in Azure Pipelines task, such as running MSBuild or VSTest, is implemented.
Learn the pattern for writing a custom pipeline task that reads credentials or writes progress back to Azure Pipelines.
Report a bug or contribute a fix to one of the existing pipeline tasks.
Package a custom task into an Azure DevOps extension for the Microsoft marketplace.
| microsoft/azure-pipelines-tasks | cinnyapp/cinny | opensumi/core | |
|---|---|---|---|
| Stars | 3,632 | 3,634 | 3,630 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Writing and testing a custom task requires an Azure Pipelines or TFS account and the TFS Cross Platform Command Line utility.
Azure Pipelines is Microsoft's service for automating software builds, tests, and deployments. When a developer pushes code, Azure Pipelines can automatically run a series of steps, such as compiling the code, running tests, and publishing the result. Each individual step in that process is called a task. This repository contains the source code for all the built-in tasks that come included with Azure Pipelines and Team Foundation Server, which is the on-premise version of the same system. Examples of tasks include running a script, building a .NET project, running tests with a specific test runner, or deploying to a cloud service. The repository is published openly by Microsoft both as a reference and as a way for the community to report bugs and suggest improvements. For most situations where you need something custom in your pipeline, Microsoft recommends using the existing script-running tasks, such as the PowerShell or Bash tasks, rather than writing a new one. But if you need something that integrates more deeply, like reading build credentials or writing structured progress records back to the Azure Pipelines interface, you can write your own task. The repository serves as a working example of how that is done. Custom tasks you write can be uploaded to Azure Pipelines using a command-line tool Microsoft provides, or packaged into an Azure DevOps extension and shared through Microsoft's marketplace. The repository accepts contributions and bug reports, and security issues should be sent to Microsoft's security team by email rather than filed publicly.
The official source code for the built-in tasks (build, test, deploy steps) that ship with Microsoft's Azure Pipelines and Team Foundation Server.
Mainly TypeScript. The stack also includes TypeScript, PowerShell, Bash.
No license terms are stated in the README.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.