-
Notifications
You must be signed in to change notification settings - Fork 166
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
Replace miniconda by micromamba in CI #257
Conversation
Using mamba-org/provision-with-micromamba@main action avoids the need of installing miniconda to install mamba.
Decouple the ggc9 and the pysteps installation tasks.
This reverts commit 8c17771
Codecov Report
@@ Coverage Diff @@
## master #257 +/- ##
=======================================
Coverage 80.92% 80.92%
=======================================
Files 142 142
Lines 10759 10759
=======================================
Hits 8707 8707
Misses 2052 2052
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah this is real nice, I didn't know about a micromamba!
@aperezhortal Nice, I was just doing the same over at |
@aperezhortal you wanna merge this or is it still work in progress? |
This PR takes #256 one step further using the
mamba-org/provision-with-micromamba@main
action to create the environment, instead ofconda-incubator/setup-miniconda@v2
Although the computational time saved is minimal (a minute at the most), it simplifies a little bit the workflow specification, condensing the previous "miniconda installation" and "environment creation" task into a single one.
More information on micromamba: https://github.com/mamba-org/mamba#micromamba