debben / vsts-helm-extension

An unofficial Helm extension for Visual Studio Team Services
MIT License
4 stars 1 forks source link

Fails on Windows Agent #2

Closed uday31in closed 6 years ago

uday31in commented 6 years ago

2017-11-23T18:23:51.3938674Z ##[section]Starting: helm dependency 2017-11-23T18:23:51.4378671Z ============================================================================== 2017-11-23T18:23:51.4378671Z Task : Work with Helm packages 2017-11-23T18:23:51.4378671Z Description : Build, install, and update helm packages. 2017-11-23T18:23:51.4378671Z Version : 0.1.0 2017-11-23T18:23:51.4378671Z Author : Don Ebben 2017-11-23T18:23:51.4378671Z Help : More Information 2017-11-23T18:23:51.4378671Z ============================================================================== 2017-11-23T18:23:52.7307830Z Downloading: https://storage.googleapis.com/kubernetes-helm/helm-v2.7.0-windows-amd64.zip 2017-11-23T18:23:52.9464515Z ##[error]Unexpected HTTP response: 404 2017-11-23T18:23:52.9634505Z ##[section]Finishing: helm dependency

debben commented 6 years ago

This looks to be related to https://github.com/kubernetes/helm/issues/3178

It seems like the Helm project has gone back and forth between offering zip and tar.gz as the download format for Windows binaries. The PR for the release checklist referenced in that issue makes it look like .tar.gz will be used going forward.

htuomola commented 6 years ago

What's the state of this? Or rather, I just installed the task and seems that this fix actually is included in the published task but it still fails on Windows.

2018-01-10T10:52:10.4810660Z filename: helm-v2.7.0-windows-amd64
2018-01-10T10:52:10.4813257Z Downloading: https://storage.googleapis.com/kubernetes-helm/helm-v2.7.0-windows-amd64.tar.gz
2018-01-10T10:52:11.3934353Z Extracting archive
2018-01-10T10:52:11.7420460Z [command]"C:\Program Files\Git\usr\bin\tar.exe" xzC d:\a\_temp\c2a1b98a-57ef-4084-bd32-863417d8f658 -f d:\a\_temp\4b31c29b-d115-4347-a94e-8b7852bbbfa3
2018-01-10T10:52:15.8509097Z tar (child): Cannot connect to d: resolve failed

I'm not an expert on Tar but seems to me that the issue is with it interpreting colons as computer names by default, see this SO answer.

Btw. this seems like a very useful task, really would make using helm easier, thanks!

debben commented 6 years ago

Sorry for the delay. I've pushed an updated version that I think should resolve the tar extract issue.