-
Notifications
You must be signed in to change notification settings - Fork 0
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
'gcloud' is not recognized as a command #67
Comments
Any updates on this? For now, I've had to create a variable manually pointing to the SDK location (e.g. FWIW, it seems the install command is appending the PATH variable as: |
@gcacars Hi, any chance you could take a look at this? Have you seen/heard similar issues? My temporary workaround is already facing issues, because I have a schedule set up for a weekly build, and has already failed so many times because the SDK version changes, so I have to manually commit the new path every time it fails. It would be really nice to get this working again. |
Hi @TMGMike sorry for the long time without a reply. I really appreciate any help from community in this. If you can, please open a PR. This is a one file task code: Inspired by official Azure CLI task: |
@gcacars Hi, no worries on the reply, I've been super busy myself so I understand :) I can try to raise a PR to fix this, if I can find some time myself. If it turns out it is just the fact that we're missing the |
@gcacars Just taking a look into the code, I see an explicit if statement to not append azure-devops-google-cloud-tools/Tasks/GoogleCloudSdkTool/gcloudcli.ts Lines 85 to 87 in 6b3ab48
Did Google change their folder structure for Windows builds, or is there another reason? Also while we're here, do you know why the versionSpec field doesn't do anything? Even when I specify a GCP SDK version, it will still always install the newest release... is it failing to find the version specified or something? |
Hi guys,
I've been using this tool to install the Google Cloud SDK on my agent machines in Azure Pipelines, and haven't noticed any issues until recently (although I took a break for a little while so there was no activity).
Installing the SDK succeeds, but when trying to authenticate with GCP (to upload build artefacts to GCS), it fails to find the command. The log shows that it has added the script to the PATH variable, so it shouldn't be failing... Unless a recent upgrade to the windows agents has caused the machine to require a reboot or something?
This is how I'm installing the SDK:
This is how I'm then authenticating (to be used when uploading the artefacts):
'gcloud' is not recognized as an internal or external command, operable program or batch file.
##[error]Cmd.exe exited with code '1'.
Finishing: Authenticate GCP
Any ideas? Did I miss a big change during my break?
Edit: I'm also noticing that no matter what version I specify in the
versionSpec
attribute, it always seems to install 392...Downloading: https://dl.google.com/dl/cloudsdk/channels/rapid/downloads/google-cloud-sdk-392.0.0-windows-x86_64.zip
- is this normal?The text was updated successfully, but these errors were encountered: