Skip to content

issues Search Results · repo:microsoft/azure-pipelines-agent language:C#

Filter by

2k results
 (84 ms)

2k results

inmicrosoft/azure-pipelines-agent (press backspace or delete to remove)

What happened? With a self hosted agent running on a Mac mini arm64, I downloaded the macOS arm64 agent 4.255.0 from this url it appear that the node executable in externals/node/bin/node and externals/node10/bin/node ...
Area: Agent
bug
triage
  • smardine
  • Opened 
    32 minutes ago
  • #5246

What happened? No usable version of the libssl was found message appears sporadically in the pipeline run log outputs at varying steps, which results in inconsistent behavior, making the runs appear flaky. ...
Area: Agent
bug
triage
  • ivobre
  • Opened 
    2 hours ago
  • #5245

What happened? This issue was discussed here: https://github.com/microsoft/azure-pipelines-agent/issues/3308 However, no solution was found. Below is an explanation of the issue, and possible solutions: ...
Area: Agent
bug
triage
  • DavidLBoyd1986
  • Opened 
    7 days ago
  • #5234

What happened? During setup of a deployment group agent, the following textual messages show up: 2025-06-03 10:17:43Z: Einstellungen wurden gespeichert. Geben Sie SERVICE_SID_TYPE_UNRESTRICTED für den ...
Area: Agent
bug
triage
  • Tornhoof
  • Opened 
    8 days ago
  • #5233

What happened? Some of our pipelines running on self hosted agents developed this problem recently. When setting up for the pipeline stage this error is recevied when checking out the source repo. Starting: ...
Area: Agent
bug
triage
  • ocdevo
  • Opened 
    8 days ago
  • #5230

What happened? My pipeline is named JAzure CI . I added this script to my pipeline: set -x echo $(Build.DefinitionName) echo $BUILD_DEFINITIONNAME It is evaluated as: ##[debug]script=set -x echo ...
Area: Agent
bug
triage
  • dagood
  • 3
  • Opened 
    13 days ago
  • #5227

Describe your feature request here WSL 2 is functional for containers on self-hosted Windows agents with a clean install, despite lacking official support. However, during agent upgrades, the bin directory ...
Area: Agent
enhancement
triage
  • npbenjohnson
  • Opened 
    20 days ago
  • #5219

What happened? The agent is stuck in the post job phase. Checking the worker logs reveals that it seems to experience some intermittent network issues when trying to connect to Azure DevOps (see log output). ...
Area: Agent
bug
triage
  • cata008
  • 1
  • Opened 
    20 days ago
  • #5218

What happened? Related Issue #4324 Description Our security scanners have detected an obsolete Node.js version (16.20.2) in the Azure Pipelines agent installation. Current Installation Path: /opt/azagent_services/externals/node16/bin/node ...
Area: Agent
bug
triage
  • gidad
  • Opened 
    22 days ago
  • #5214

What happened? Getting warning: ##[warning]The operating system version this agent is running on (almalinux OS name: 9.4) is not supported on an upcoming update to the Pipelines Agent. For supported operating ...
Area: Agent
bug
triage
  • rkontrimas
  • Opened 
    23 days ago
  • #5213
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue search results · GitHub