-
Notifications
You must be signed in to change notification settings - Fork 867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Pipeline fails since upgrade to agent 3.227.2 #4472
Comments
Hi @Kralizek, thank you for the feedback. T Also, please ensure that some of your steps do not modify/remove env variables as well as dotnet itself. |
@DmitriiBobreshev this is the log of the Initialize Job step
|
For sake of completeness, the pipeline installs and uses the .NET SDK 8 but it had successful runs even after .NET 8 RC2 was releases so I didn't think it was a factor
|
@Kralizek Seems like the problem is not exactly in the dotnet version but in the dotnet-coverage version. I was able to reproduce the error with dotnet 8 + dotnet-coverage 17.8.6 but seems like it happened because of the dotnet-coverage version after I changed the package version from 17.8.6 to the latest 17.9.1, everything started working fine. Could you please try to set dotnet-coverage to 17.9.1 in your dotnet-tools.json file? |
@DmitriiBobreshev thanks a lot! upgrading dotnet-coverage to 17.9.1 actually solved the issue. but I am not super happy that a new tool version can break a build. It makes pinning a version useless. |
@Kralizek, Closing the issue. The problem is not related to the agent/tasks but to dotnet.
Please feel free to reopen if you have additional questions, but I believe it is better to create a ticket in the dotnet repository if you want to understand the bug's behaviour. |
What happened?
A pipeline started failing without any changes. These are the relevant parts of the pipeline.
Here is the dotnet-tools.json file
Here is the relevant output on the pipelines:
Versions
Looking at the pipeline logs, I noticed that the agent version changed from 3.277.1 (working) to 3.277.2 (broken).
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
No response
Version controll system
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: