Azure Pipelines Agent

Announcement - `AZP_AGENT_USE_LEGACY_HTTP` agent knob future deprecation

We are working on pipeline agent migration to .NET 6. One of the side effect of this migration is that the legacy HTTP handler will be no longer available for use due to changes in the .NET runtime itself.

Thus the related agent knob will not work once the migration will be completed. We recommend stopping using the AZP_AGENT_USE_LEGACY_HTTP knob.

Overview

The cross-platform build and release agent for Azure Pipelines and Team Foundation Server 2015 and beyond. This replaced the deprecated closed source windows build agent and the previous cross-platform agent.

Supported on Windows, macOS, and several Linux flavors. Written for .NET Core in C#.

Status

	Build & Test
Windows x64
Windows x86
macOS
Linux x64
Linux ARM
RHEL 6 x64

Get the Agent

Get started with the agent.

Supported Usage

This agent can be used for Azure Pipelines, Azure DevOps Server 2019+, and TFS 2017+. It also replaces the Node-based agent for TFS 2015.

Scenario	Mac/Linux	Windows	Comment
Azure Pipelines	Yes	Yes
TFS2015 (onprem)	Yes	No	Windows use agent with 2015
TFS2017 (onprem)	Yes	Yes
TFS2018 (onprem)	Yes	Yes

Latest and Pre-release labels for releases

Releases have labels Latest and Pre-release. Please make a note that the labels mean:

Latest - release process of the agent version is fully completed and it's available for all users;
Pre-release - release process of the agent version was started and it's already available for using by part of users.

Each new version of agent is released for users by groups during several days. And usually it becomes available for all users within 6-8 days after start of release. The release has label "Pre-release" during all these days. So it's expected behavior if specific release is used by builds in pipelines but it's marked as "Pre-release".

Troubleshooting

Troubleshooting tips are located here

Contribute

For developers that want to contribute, read here on how to build and test.

Issues

We accept issue reports both here (file a GitHub issue) and in Developer Community.

Do you think there might be a security issue? Have you been phished or identified a security vulnerability? Please don't report it here - let us know by sending an email to secure@microsoft.com.

License

magnologan/azure-pipelines-agent

ErrorLooks like something went wrong!

About

Resources

License

Code of conduct

Security policy

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Languages

Error
Looks like something went wrong!

Packages