-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
refactor build_with_mambabuild bool with conda_build_tool choice #1732
Conversation
…-build-tool-choices
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.
I do not see any obvious problems. We'll need to test this live before merging.
A few DNM PRs to test this live:
Edit: Interestingly, all Windows builds reported an exit code of 1 despite having passed the build and tests successfully 🤔 |
Think it might help for us to ship Maybe this simplifies the install commands (or even removes the need for them) |
set "CONDA_SOLVER=libmamba" | ||
conda.exe build "{{ recipe_dir }}" -m .ci_support\%CONFIG%.yaml --suppress-variables %EXTRA_CB_OPTIONS% |
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.
Would it makes sense to either specify this by the --solver
flag or better yet add this to the .condarc
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.
conda-build
doesn't have the --solver
flag so the other alternative is writing to .condarc
, but that will have global impact on the other uses of conda
so I initially wanted to constrain the scope as much as possible (in case something breaks).
I am happy to revisit that in the future as we debug it step by step.
Thanks Jaime! 🙏 Had a couple questions above |
The strange Windows exit_code=1 issues are gone if we use conda 23.7 and conda-build 3.26 🤷 |
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.
Lgtm! Some comments on repetition in the templates but also the code blocks are clear so I think we should merge!
LGTM! |
Checklist
news
entryRefactoring the
build_with_mambabuild
boolean option with a more future-proofconda_build_tool
"list of choices". I have added support for:mambabuild
conda-build
withconda-libmamba-solver
conda-build
with (forced)classic
solverconda-build
(no specific solver configuration)In a hypothetical future, this setup would also allow us to have
boa
andrattler-build
, for example.build_with_mambabuild=True
maps toconda_build_tool=mambabuild
. Thefalse
equivalent maps toconda_build_tool=conda-build
.Note that the default behaviour (using
mambabuild
) has not changed.Why this change now?
This just adds opt-in support for conda-libmamba-solver. I am working on improving the integration with conda-build in conda/conda-libmamba-solver#194. While the current released implementation works for single output recipes, I think it might not work correctly with multi-output stuff, or maybe with multi-recipe calls.