Skip to content
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

Move GHA to setup-micromamba #2545

Merged
merged 11 commits into from
Jun 15, 2023
Merged

Conversation

AntoinePrv
Copy link
Member

No description provided.

@AntoinePrv AntoinePrv force-pushed the ci-setup-micromamba branch 2 times, most recently from 2fb8f62 to f669fa5 Compare June 12, 2023 12:44
@pavelzw
Copy link
Member

pavelzw commented Jun 15, 2023

Thanks for fixing what I gave up on!

extra-specs: menuinst

create-args: menuinst
init-shell: bash cmd.exe powershell
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Setting init-shell: none could also be an option. This would then definitely not interfere with the shell initialization tests...

We would then need to activate the micromamba environment by hand or call micromamba run -n ...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think when init-shell was not used, the shell was not finding micromamba executable

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is because the micromamba executable is not on PATH. You could add it to PATH manually beforehand:

      - name: Add micromamba to GITHUB_PATH
        run: echo "${HOME}/micromamba-bin" >> "$GITHUB_PATH"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

provision-with-micromamba did the shell initialization thing for every shell that was on the system. setup-micromamba allows you to specify the shell and also gives you the option to do the initialization for no shell at all. I think this would be the option that makes the most sense for shell init tests.

Copy link
Collaborator

@jonashaag jonashaag Jun 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May I lobby for #2577

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

provision-with-micromamba did the shell initialization thing for every shell that was on the system. setup-micromamba allows you to specify the shell and also gives you the option to do the initialization for no shell at all. I think this would be the option that makes the most sense for shell init tests.

I agree this would be better, but I'm also afraid by potential issues this could lead to and the time it would take to fix them. Let's merge this one since it passes the, and and tackle this in a dedicated PR.

.github/workflows/main.yml Outdated Show resolved Hide resolved
.github/workflows/main.yml Outdated Show resolved Hide resolved
.github/workflows/main.yml Outdated Show resolved Hide resolved
.github/workflows/main.yml Outdated Show resolved Hide resolved
.github/workflows/main.yml Outdated Show resolved Hide resolved
.github/workflows/main.yml Outdated Show resolved Hide resolved
.github/workflows/main.yml Outdated Show resolved Hide resolved
.github/workflows/main.yml Outdated Show resolved Hide resolved
@jonashaag
Copy link
Collaborator

LGTM, I think all of the micromamba activate build_env can go, will try that in a new PR

@AntoinePrv AntoinePrv merged commit 7b0b9a5 into mamba-org:main Jun 15, 2023
20 checks passed
@AntoinePrv AntoinePrv deleted the ci-setup-micromamba branch June 15, 2023 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants