-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Flaky build: Failed while installing version: 3.1.100 at path: #12120
Comments
We have an issue filed for this in the DevOps task microsoft/azure-pipelines-tasks#12613. |
@chidozieononiwu lets see what options we have to potentially by-pass this task and setup the correct version on the path, or maybe we can just rely on the global.json configuration to pick the correct version (assuming it is already on the image). |
Yes we can specify sdk version in globals.json. I don't think we need to use any of the net Core Installer tasks as the version are already installed on the agents. Here is a job I ran without using them https://dev.azure.com/azure-sdk/internal/_build/results?buildId=509589&view=results |
I think we still need to set the RuntimeFrameworkVersion as I don't think we can easily control that with global.json. Can you also do a test that verifies if the version of the SDK we specify in global.json isn't on the machine that it fails correctly? |
Yes, it will throw an error if the correct sdk version is not found. |
As for whether or not the task caches the tools I found microsoft/azure-pipelines-tasks#10405 which states it does cache the tools but only if they were downloaded from that task. It currently does not locate and use any pre-installed tools on the image. |
https://dev.azure.com/azure-sdk/public/_build/results?buildId=394547&view=logs&jobId=b08a78d6-c9ce-53c1-53b1-9a5d436f78f6&j=b08a78d6-c9ce-53c1-53b1-9a5d436f78f6&t=05d13a84-370b-58cf-019b-9a3a12c3c6fe
cc @weshaggard @chidozieononiwu
The text was updated successfully, but these errors were encountered: