-
Notifications
You must be signed in to change notification settings - Fork 4
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
Versions #18
Comments
Thanks for posting the issue @intotecho . The issue is caused by using an unsupported python version (3.9) for GCP SDK v306. Python 3.9 is supported from GCP SDK v318 onwards. See support ticket. Switching to GCP SDK v375, therefore, should have worked on win-2022. Could you share your pipeline so I'm able to understand why it resolved to the wrong GCP SDK version? |
Created an example pipeline that installs GCP SDK v306 on Windows 2022. Note the UsePythonVersion task to downgrade the python version to 3.8. Also note the pool:
name: windows-2022
steps:
- task: UsePythonVersion@0
name: usePython
displayName: Use Python 3.8
inputs:
versionSpec: 3.8
- task: CmdLine@2
displayName: Set CLOUDSDK_PYTHON
inputs:
script: 'echo ##vso[task.setvariable variable=CLOUDSDK_PYTHON]$(usePython.pythonLocation)\python.exe'
- task: GoogleCloudSdkInstaller@0
displayName: Install Google Cloud SDK 306.0.0
inputs:
version: 306.0.0
- task: GcloudRunner@0
displayName: gcloud components list
inputs:
command: components list |
We had this working on SDK v306 and vscode-windows-2016 for while.
After changing to SDK v375 it caused a path error. i.e. it thinks the path is still //306//
Moving Agent specification to windows-2022 failed with a python exception
Changing Agent Specification to
ubuntu-20.04
works great with GCP SDK 375.We don't need those older versions to work, but a release note specifying which agents are supported would be useful.
The text was updated successfully, but these errors were encountered: