You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the update to the 1.7.x version, the MicrosoftSecurityDevOps@1 started to fail in Azure DevOps self-hosted agents configured behind a proxy
It's failling in both Windows and Linux agents. The below logs are from Windows2022 agents
Did this problem ever progress to a workaround or even a solution ? We have upgrade just recently to v3.230.2 and now have issues with our self hosted agents on premise. Our Azure hosted agents are running a-ok.
As far as i can see the node.exe that runs index.js ( "C:\agent\externals\node16\bin\node.exe" "C:\agent_work_tasks\MicrosoftSecurityDevOps_XYZ\1.11.0\index.js") doesn't honor the proxy setup,
Testing with procmon64.exe shows that node.exe connects to the public IP's on 443 for the MicrosoftSecurityDevOps task.
Examples working with node.exe :
AzureKeyVault 1.232.0 run.js
UseDotNet 2.232.0 usedotnet.js
Not working with node.exe :
MicrosoftSecurityDevOps 1.11.0 index.js
After the update to the 1.7.x version, the MicrosoftSecurityDevOps@1 started to fail in Azure DevOps self-hosted agents configured behind a proxy
It's failling in both Windows and Linux agents. The below logs are from Windows2022 agents
In previous versions, 1.6.x ,when it had dependency on dotnet, execution was fine
Example failing task
Log:
The text was updated successfully, but these errors were encountered: