-
-
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
Initial Drone support #1069
Initial Drone support #1069
Conversation
Thanks for putting this in @jmreicha! |
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.
Hrm, yeah that makes sense.
@isuruf How would I access the value of docker_image
in the template? I see the correct image in the rendered output, just not sure how to get it into the configuration file.
See #1070. You can rebase on top of that PR or merge that PR here. |
Can you merge this branch with master? |
I think changes still need to be made to If somebody else wants to take it over that would be great, otherwise progress will be much slower. |
template_files = platform_templates.get(platform, []) | ||
|
||
# Explicitly add in a newline character to ensure that jinja templating doesn't do something stupid | ||
build_setup = "run_conda_forge_build_setup\n" |
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.
Can you use _get_build_setup_line
here?
Looks good to me. We can merge this now and work on CI registration later. |
Thanks so much for this! |
I've gone ahead and raised issue ( #1079 ) to track this. |
Checklist
news
entryResolves conda-forge/conda-forge.github.io#269.
This PR aims to add native aarch64/armv8 builds to Conda forge. Currently the Arm builds are emulated using QEMU and leverage Azure pipelines. The main issues with this approach is that Azure limits the number of CPUs for builds to 2, so large builds are slow and relying on QEMU for Arm emulation can potentially have side effects.
Adding Drone support alleviates these issues by offering native aarch64/armv8 build support as well as offering many more CPUs for builds, which should significantly speed up builds and reduce build times and avoid potential bugs/side effects.