[BUG]: UseDotnetV2 - Fails silently to download #20508
Comments
|
We have the same issue here since this morning. Was there a recent update to the task? |
v-schhabra
added
Area: ABTT
|
We are having this issue since this morning too. |
|
Same issue started today morning for our .NET builds on Self-Hosted agents. |
|
Thanks for raising this issue to us. As per recent changes:
|
|
I rolled back to 2.243.1 which was working a few days / weeks ago and I have the same output of download not always waited without raising any error, so following tasks using dotnet are failing. |
|
We also been having the same issue since this morning, Version : 2.246.1 |
|
We have the same issue since yesterday: @JasonWhall it also happens / fails on MS Hosted, thus you could check also that box in the description:
|
|
We have encountered the same issue on multiple pipelines and this is impacting our deliverables. Could this please be escalated or priority elevated? Thank you in advance |
|
Hi @DergachevE , could this issue be escalated? This is creating a huge impact in our dev teams unfortunately. |
|
We seem to be having the same problem but it doesn't always happen for us. I have no idea why it does or doesn't work. Agent name: 'Hosted Agent' The task downloads the zip file, then finishes without extracting/installing the sdk. The next step is restoring nuget packages but this fails because the sdk version is not found.
|
|
It happens about 50% of the time for us. I see reverting to version 2.243.1 did not help a poster above. Perhaps reverting to an even earlier version would help? |
Unfortunately the issue happens even with previous versions. We rolled back to 2.238.1 and still same problem, build failing 50% of the time. |
|
Today I saw this in the logs if this is of help: |
|
As a workaround if you use a custom image for you agent as we do (self-hosted agent pool on AKS), then you can just bake in the dotnet sdk: I see that our builds where dotnet failed to download are now passing. Download failure rate is quite high, more than 50%. |
|
We started getting the above errors from 30 minutes ago. The issue now seems like happening 100% of the time. |
|
Hi folks, as a quick workaround we suggest using the following scripts before the for windows: - powershell: |
# your target dotnet version
$version = "8.0.107"
# your target install path
$sdkInstallationPath = Join-Path $env:AGENT_TOOLSDIRECTORY dotnet
$scriptUrl = "https://dot.net/v1/dotnet-install.ps1"
$scriptPath = Join-Path $env:AGENT_TEMPDIRECTORY dotnet-install.ps1
Invoke-WebRequest -Uri $scriptUrl -OutFile "$scriptPath"
& $scriptPath -Version $version -InstallDir $sdkInstallationPath -Verbose
"$version" > "${sdkInstallationPath}\sdk\${version}.complete"
condition: eq(variables['Agent.OS'], 'Windows_NT')for linux & macos: - bash: |
# your target dotnet version
version="8.0.107"
# your target install path
installationPath="$(Agent.ToolsDirectory)/dotnet"
script_path="$(Agent.TempDirectory)/dotnet-install.sh"
curl -o $script_path "https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.sh"
chmod +x $script_path
$script_path --version $version --install-dir $installationPath --verbose
echo "$version" > "${installationPath}/sdk/${version}.complete"
condition: ne(variables['Agent.OS'], 'Windows_NT')With these scripts, !!!! Please make sure |
Hi @DergachevE, Thank you for recognizing this is an issue, but would it be possible to escalate the severity of this up a few notches? We're currently heavily affected by this issue, and it's wrecking havoc across multiple pipelines. |
|
Hi @DergachevE Yes, please give the rollout a priority, this is terrible for a couple of days now. Most of our Builds are failing because of that, and we have to rerun it manually. And the Workarounds are not really suitable for us. |
|
Hi @DergachevE and @KonstantinTyukalov! We see builds failing due to the same issue. While I appreciate the provided workarounds, is there a way to escalate this issue to speed up a resolution? Thank you. |
|
Here's a script for installing dotnet runtime, not full SDK: - powershell: |
# your target dotnet version
$version = $env:version;
# your target install path
$sdkInstallationPath = Join-Path $env:AGENT_TOOLSDIRECTORY dotnet
$scriptUrl = "https://dot.net/v1/dotnet-install.ps1"
$scriptPath = Join-Path $env:AGENT_TEMPDIRECTORY dotnet-install.ps1
Invoke-WebRequest -Uri $scriptUrl -OutFile "$scriptPath"
& $scriptPath -Runtime dotnet -Version $version -InstallDir $sdkInstallationPath -Verbose
"$version" > "${sdkInstallationPath}\shared\Microsoft.NETCore.App\${version}.complete"
displayName: Installing .NET
env:
version: 3.1.32 |
|
Also had to change to After all, this is the code that worked: - powershell: |
# your target dotnet version
$version = $env:version;
# your target install path
$sdkInstallationPath = "C:\Program Files\dotnet"
$scriptUrl = "https://dot.net/v1/dotnet-install.ps1"
$scriptPath = Join-Path $env:AGENT_TEMPDIRECTORY dotnet-install.ps1
Invoke-WebRequest -Uri $scriptUrl -OutFile "$scriptPath"
& $scriptPath -Runtime dotnet -Version $version -InstallDir $sdkInstallationPath -Verbose
Get-ChildItem "$sdkInstallationPath\shared\Microsoft.NETCore.App"
"$version" > "$sdkInstallationPath\shared\Microsoft.NETCore.App\${version}.complete"
displayName: Installing .NET
env:
version: 3.1.32 |
|
Same issue here, happens randomly (maybe 50% of runs fail). Starts downloading the SDK, returns early and subsequent nuget installation fails. |
|
I made a pipeline with the following steps, and ran it a few times: The result was the following:
Please prioritize a fix for this. |
KonstantinTyukalov
added
the
awaiting deployment
|
Hi everyone, we are currently releasing fixed task versions - Thanks |
|
2.247.1 first run succeeded (will watch it). 15 minutes ago with 246.1 was failing. |
|
First few builds using 2.247.1 were successful. Will report back once I have more data. |
Hallelujah! Sorry for my frustration, but sometimes I think we developers, users of these products, are not only paying users, but are also considered your QA. |
|
Also seems to work nicely for us. Thanks! |
|
The fix works fine for us. |
|
Thanks everyone for your patience! @sicil1ano I understand your frustration. |
and others
New issue checklist
Task name
UseDotnet
Task version
2.246.1
Issue Description
It seems the task is silently stopping after attempting to download the zip containing a version of the .NET sdk and then continues onto the next step. I would expect this to either error and fail the task or to successfully log that it has downloaded the tool and extracted into the tool directory
The offending area of code that it seems to be exiting from is in the azure-pipelines-tool-lib repository noted here - https://github.com/microsoft/azure-pipelines-tool-lib/blob/41acd733ff90c8bbc02c42376f46800b794cdc99/tool.ts#L251
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Server Latest/Ubuntu Latest
Relevant log output
The text was updated successfully, but these errors were encountered: