Do not move micromamba cache to `%MINIFORGE_HOME%`

conda-forge / conda-smithy

The tool for managing conda-forge feedstocks.

https://conda-forge.org/

BSD 3-Clause "New" or "Revised" License

152 stars 183 forks source link

Do not move micromamba cache to `%MINIFORGE_HOME%` #2107

Closed jaimergp closed 3 weeks ago

jaimergp commented 4 weeks ago

Checklist

[x] Added a news entry
[X] Regenerated schema JSON if schema altered (python conda_smithy/schema.py)

Patches symptom behind https://github.com/conda-forge/conda-smithy/issues/2101, but at the cost of not reusing the micromamba cache for conda-build on Windows. It should have a minor impact in the timings, given how fast the CI download is anyway. The mamba team has been notified of the issue and will be looking into it, so we can revert the workaround in the future, once fixed.

jaimergp commented 3 weeks ago

Tested at conda-forge/arrow-cpp-feedstock@d007a0e (#1432) and it works