GEOPY-2809: Python env for Analyst on current packages from develop

[sebhmg]

GEOPY-2809 - Python env for Analyst on current packages from develop
for https://github.com/MiraGeoscience/geopy-distrib/pull/89

[Copilot]

Pull request overview

Updates the Azure Pipelines “minimal conda env install” template to target Python 3.12 and adjust repository/environment mapping and environment-file discovery to align with updated lockfile generation/naming.

Changes:

• Bumped the default pythonVersion parameter from 3.10 to 3.12.
• Updated envToVirtualRepos defaults from single repo strings to lists (to support multiple virtual repos per environment).
• Changed the environment lockfile discovery glob to a new *-py<ver>-win-64.conda.lock.yml naming convention.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sebhmg]

The pipeline collects correctly the environment files but fails on docker login. See failure at: https://dev.azure.com/mirageoscience/DevOps/_build/results?buildId=3428&view=results

Fixing this part is beyond the scope of GEOPY-2809.
Created DEVOPS-1139 to address that failure

[RomFloreani]

Looks good! Just see Copilot comment on the pattern for the new file name.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

[sebhmg]

ran here: https://dev.azure.com/mirageoscience/DevOps/_build/results?buildId=3443&view=results

But it seems it did not find the env file. Must have missed something in last commits

[sebhmg]

better explicit failure message if no env files are collected. See here: https://dev.azure.com/mirageoscience/DevOps/_build/results?buildId=3444

[sebhmg]

env files now successfully collect here: https://dev.azure.com/mirageoscience/DevOps/_build/results?buildId=3445&view=artifacts&pathAsName=false&type=publishedArtifacts

Still fails on the creation of the Docker container. To be fixed by DEVOPS-1139