Devops pipeline convert python version 3.10 to 3.1

wangzelin007 commented 1 year ago

Note

Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo

For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

If you have an issue or request for the Azure Pipelines service, use developer community instead:

https://developercommunity.visualstudio.com/spaces/21/index.html )

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug

Enter Task Name: Simple Job Task

list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

Environment

Server - Azure Pipelines or TFS on-premises?
- If using TFS on-premises, provide the version:
- If using Azure Pipelines, provide the account name, team project name, build definition name/build number:
Agent - Hosted or Private:
- If using Hosted agent, provide agent queue name:
- If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description

[Include task name(s), screenshots and any other relevant details] I defined the following python version to test our code. There is no problem with other python versions, except python3.10, which is parsed as python 3.1. This is obviously wrong, and even though I'm putting 3.10 in quotes, it doesn't help. Build url: https://dev.azure.com/azclitools/public/_build/results?buildId=18812&view=logs&j=eb5b53a1-0133-57f5-2863-59dfa7e67ead&t=e0d84c3f-9315-5988-ade5-ff2722b1cce8

Task logs

[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]

Troubleshooting

Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting

Error logs

[Insert error from the logs here for a quick overview] 2022-12-02T05:21:08.0425663Z ##[section]Starting: Use python310 2022-12-02T05:21:08.0433117Z ============================================================================== 2022-12-02T05:21:08.0433390Z Task : Use Python version 2022-12-02T05:21:08.0433669Z Description : Use the specified version of Python from the tool cache, optionally adding it to the PATH 2022-12-02T05:21:08.0433945Z Version : 0.206.0 2022-12-02T05:21:08.0434126Z Author : Microsoft Corporation 2022-12-02T05:21:08.0434431Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/tool/use-python-version 2022-12-02T05:21:08.0434752Z ============================================================================== 2022-12-02T05:21:08.5212832Z ##[warning]You should provide GitHub token if you want to download a python release. Otherwise you may hit the GitHub anonymous download limit. 2022-12-02T05:21:08.5597916Z ##[error]Failed to download Python from the Github Actions python registry (https://github.com/actions/python-versions). Error: Error: Could not find Python matching spec 3.1 (x64) in the python-versions registry. Beware that only systems listed in the Github Actions python versions manifest (https://github.com/actions/python-versions/blob/main/versions-manifest.json) are fit for downloading python on-flight. Also, proxy is not supported. 2022-12-02T05:21:08.5652942Z ##[error]Version spec 3.1 for architecture x64 did not match any version in Agent.ToolsDirectory. Versions in /opt/hostedtoolcache:

2.7.18 (x64) 3.10.8 (x64) 3.11.0 (x64) 3.6.15 (x64) 3.7.15 (x64) 3.8.14 (x64) 3.9.15 (x64) If this is a Microsoft-hosted agent, check that this image supports side-by-side versions of Python at https://aka.ms/hosted-agent-software. If this is a self-hosted agent, see how to configure side-by-side Python versions at https://go.microsoft.com/fwlink/?linkid=871498. 2022-12-02T05:21:08.5691179Z ##[section]Finishing: Use python310

max-zaytsev commented 1 year ago

Hi @wangzelin007 Thanks for reporting the issue. We are currently working on higher priority issues. But we'll get back to that soon.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

vittoriocanilli commented 1 year ago

Still an issue. For me it worked with single quotes until the last time I have run the pipeline in April 2023:

parameters:
  - name: pythonDockerImages
    displayName: Python versions (if a version ends with 0, you must write it between quotes)
    type: object
    default:
    - name: '3_8'
      version: '3.8'
      fullVersion: '3.8'
    - name: '3_9'
      version: '3.9'
      fullVersion: '3.9'
    - name: '3_10'
      version: '3.10'
      fullVersion: '3.10'
    - name: '3_11'
      version: '3.11'
      fullVersion: '3.11'
    - name: '3_12'
      version: '3.12'
      fullVersion: '3.12-rc'

But now I have tried to run the pipeline without changing the definition of those parameters and the single quotes are removed from the Azure Pipelines GUI, so I end up having 3.10 interpreted as 3.1 as it happens to @wangzelin007 . The only way to solve it is adding the quotes around 3.10 on the Azure Pipelines GUI every time I launch the pipeline manually, while it will fails when it is automatically triggered.

@max-zaytsev I understand that you are working on higher priority issues, but if you could suggest a valid workaround, it would be highly appreciated. Thanks in advance.

vittoriocanilli commented 1 week ago

@max-zaytsev I have managed to solve my issue by migrating my pipeline to Jenkins and deleting my Azure DevOps organisation.

microsoft / azure-pipelines-tasks