azure-pipelines - 如何强制我的 Azure 管道使用 .NET 5.0 构建?

标签 azure-pipelines .net-5

我们已经开始将一些库迁移到 net 5.0,并且需要在 Azure 管道中构建这些库。

我们的管道设置为使用特定的 SDK 版本,使用步骤“使用 .NET Core SDK”。当我们指定版本 5.0.101 时,此步骤失败。

enter image description here

由于此错误而失败

Tool to install .NET Core SDK version 5.0.101. ##[error]Failed to download or parse releases-index.json with error: {"errno":"ENOTFOUND","code":"ENOTFOUND","syscall":"getaddrinfo","hostname":"dotnetcli.blob.core.windows.net","host":"dotnetcli.blob.core.windows.net","port":443} Finishing: Use .NET Core SDK 5.0.101

最佳答案

我认为这类似于 GitHub issue #10969 。它与内部 GitHub repo/url 有关。这是因为version我们在任务中指定的内容在 releases-index 文件中搜索,该文件也可供公众访问:

enter image description here

<强> releases-index:

{
    "releases-index": [
        {
            "channel-version": "5.0",
            "latest-release": "5.0.1",
            "latest-release-date": "2020-12-08",
            "security": false,
            "latest-runtime": "5.0.1",
            "latest-sdk": "5.0.101",
            "product": ".NET",
            "support-phase": "current",
            "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/5.0/releases.json"
        },
        {
            "channel-version": "3.1",
            "latest-release": "3.1.10",
            "latest-release-date": "2020-11-10",
            "security": false,
            "latest-runtime": "3.1.10",
            "latest-sdk": "3.1.404",
            "product": ".NET Core",
            "support-phase": "lts",
            "eol-date": "2022-12-03",
            "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/3.1/releases.json"
        },
        {
            "channel-version": "3.0",
            "latest-release": "3.0.3",
            "latest-release-date": "2020-02-18",
            "security": false,
            "latest-runtime": "3.0.3",
            "latest-sdk": "3.0.103",
            "product": ".NET Core",
            "support-phase": "eol",
            "eol-date": "2020-03-03",
            "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/3.0/releases.json"
        },
        {
            "channel-version": "2.1",
            "latest-release": "2.1.23",
            "latest-release-date": "2020-10-13",
            "security": false,
            "latest-runtime": "2.1.23",
            "latest-sdk": "2.1.811",
            "product": ".NET Core",
            "support-phase": "lts",
            "eol-date": "2021-08-21",
            "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/2.1/releases.json"
        },
        {
            "channel-version": "2.2",
            "latest-release": "2.2.8",
            "latest-release-date": "2019-11-19",
            "security": true,
            "latest-runtime": "2.2.8",
            "latest-sdk": "2.2.207",
            "product": ".NET Core",
            "support-phase": "eol",
            "eol-date": "2019-12-23",
            "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/2.2/releases.json"
          },
        {
            "channel-version": "2.0",
            "latest-release": "2.0.9",
            "latest-release-date":"2018-07-10",
            "security": true,
            "latest-runtime": "2.0.9",
            "latest-sdk": "2.1.202",
            "product": ".NET Core",
            "support-phase": "eol",
            "eol-date": "2018-10-01",
            "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/2.0/releases.json"
        },
        {
            "channel-version": "1.1",
            "latest-release": "1.1.13",
            "latest-release-date": "2019-05-14",
            "security": true,
            "latest-runtime": "1.1.13",
            "latest-sdk": "1.1.14",
            "product": ".NET Core",
            "support-phase": "eol",
            "eol-date": "2019-06-27",
            "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/1.1/releases.json"
        },
        {
            "channel-version": "1.0",
            "latest-release": "1.0.16",
            "latest-release-date": "2019-05-14",
            "security": true,
            "latest-runtime": "1.0.16",
            "latest-sdk": "1.1.14",
            "product": ".NET Core",
            "support-phase": "eol",
            "eol-date": "2019-06-27",
            "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/1.0/releases.json"
        }
    ]
}

而且,如果您检查一下,https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/5.0/releases.json 也可以公开访问。因此,我确信内部提到的 URL 是错误的,因此代理会抛出 NOT FOUND 错误。

在这种情况下,我建议您重新打开 Issue #10969并通知产品团队。

关于azure-pipelines - 如何强制我的 Azure 管道使用 .NET 5.0 构建?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/65396246/

相关文章:

Azure DevOps中的Flutter管道

c# - ProtoBuf-Net错误: No serializer defined for type of inner class

windows - 如何授予 Azure Devops 私有(private) Windows 代理访问 SupportedAPIs-x64.xml 的权限?

azure-devops - Azure DevOps 无法从其自己的存储库下载工件

git - 如何排除对管道 yaml 文件的更改以触发构建 i azure devops?

c# - 如何从 C# 方法添加 Razor 标记?

c# - 在asp.net core Controller 中获取 "Request Payload"

c# - 无法在 .NET Core 中创建动态类型

c# - 如何处理第三方代码中的死锁

api - 无法使用 Az DevOps Pipelines API 6.0-preview.1 创建新管道