-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
WIP: Use multiple docker images #6
WIP: Use multiple docker images #6
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
In order to ensure the `docker_image` is incorporated into re-rendering, this adds the variant to a special section within `extra`.
…da-forge-pinning 2019.07.23 Now that the `docker_image` variant is included in the `meta.yaml`, re-render to update the feedstock configuration files to each use their own Docker image.
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
@@ -72,3 +72,6 @@ extra: | |||
- Akshay-Venkatesh | |||
- jakirkham | |||
- TomAugspurger | |||
|
|||
variants: | |||
docker_image: {{ docker_image }} |
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.
Adds the variant to extra
to ensure that conda-build will recognize this is used and create the full matrix.
Thanks @jjhelmus for the suggestion. 🙂
ENH Add CDT for `libibcm-devel`
Attempts to use multiple Docker images for the build.
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)