-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[REGRESSION]: FuncToolsInstaller fails when using version "latest" #20642
Comments
There is also a related issue in azure-functions-core-tools repo. Indeed this could be due to a change in the versioning pattern that includes an additional prepended 'v'. |
Unless the file structure for azure function core tools is reverted, I think that the problem needs to be fixed in the pipeline task.
The same version string, neither "v4.0.6543" nor "4.0.6543", will work in both places of the download URL, 'https://github.com/Azure/azure-functions-core-tools/releases/download/%s/Azure.Functions.Cli.%s.%s.zip'. The "v" prefix is necessary in the first location but shouldn't be there in the second location. |
For now, I made it work for my pipeline by forcing it to use the older version but this need to be resolved:
|
Maybe change the pipeline task to use the link provided in the feed as |
@mnemcik-visma It's a bit more tricky than that. There are several assets in the release bundle, each with a specified |
That is exactly what I'd do by design rather than create a strong dependency on file naming conventions defined in a 3rd party repository. |
Hi @mvldk @Ehsanshiri @rrr-michael-aquilina @mnemcik-visma |
Hi @v-schhabra |
Reverted back to 4.0.6280, all works fine with this version. |
Since they changed the release file structure back in I would still suggest to follow through on the suggestion from @mnemcik-visma to rely on the release meta data instead of fragile naming convention:
I do get the same error as @mnemcik-visma with version
|
@mvldk Now I observed that the issue is no more occurring with 4.0.6543 version as well. The releases are getting successful. |
Closing this github ticket as issue has been fixed by Functoolinstaller team. |
New issue checklist
Task name
FuncToolsInstaller
Breaking task version
0
Last working task version
0
Regression Description
Azure function core tools seems to have changed their release download file structure - notice the added "v" before the version number in the folder:
https://github.com/Azure/azure-functions-core-tools/releases/download/v4.0.6594/Azure.Functions.Cli.linux-x64.4.0.6594.zip
https://github.com/Azure/azure-functions-core-tools/releases/download/v4.0.6543/Azure.Functions.Cli.linux-x64.4.0.6543.zip
https://github.com/Azure/azure-functions-core-tools/releases/download/4.0.6280/Azure.Functions.Cli.linux-x64.4.0.6280.zip
https://github.com/Azure/azure-functions-core-tools/releases/download/4.0.5907/Azure.Functions.Cli.linux-x64.4.0.5907.zip
https://github.com/Azure/azure-functions-core-tools/releases/download/4.0.5858/Azure.Functions.Cli.linux-x64.4.0.5858.zip
As a result, FuncToolsInstaller fails to download the tools when configured with version "latest": Error: Unexpected HTTP response: 404 (see logs)
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
ubuntu-22.04
Relevant log output
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: