You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wondering is there any plans to optionally run conda-press as part of conda-forge CI?
The issue is that as long as a separate CI needs to be setup for each platform (#40) the effort to build wheels (e.g. with the setup from https://github.com/MacPython) is not that much higher than setting up CI for conda-press (well at least for not too complicated projects).
To run it as part of conda-forge I imagine it would be necessary to change the CI scripts and add some optional flag to meta.yaml.
Then wheels need to be uploaded somewhere: maybe an S3 bucket or possibly we could use the same account (different bucket) that is provided for free by Rackspace for the wheels built in MacPython org.
Another point is that conda-press might need to be adapted to work for locally built packages that are not yet uploaded to a conda channel.
The text was updated successfully, but these errors were encountered:
Hi @rth ,
We do have some plans do integrate it with conda-forge.
I was working on it, I stopped a bit just to work on pytest-replay and to add some infra in conda-build which I saw more urgency let's say.
But I will get it right after it. It is on my to-do list. I just need to add one more functionality to conda-press to recursively get the conda packages and after that, the integration with conda-smithy will be easy and we can optionally add it.
The original idea was to add a conda-press.yaml on the feedstock root, if it is present it will run conda-press with the options in there, we can also develop some features to upload it somewhere (I didn't think that carefully yet).
Also, @rth, anyone is welcome to help out with this 😉 @marcelotrevisani has done an amazing job of helping get us going on the feedstocks CI, but more hands are always welcome!
Just wondering is there any plans to optionally run conda-press as part of conda-forge CI?
The issue is that as long as a separate CI needs to be setup for each platform (#40) the effort to build wheels (e.g. with the setup from https://github.com/MacPython) is not that much higher than setting up CI for conda-press (well at least for not too complicated projects).
To run it as part of conda-forge I imagine it would be necessary to change the CI scripts and add some optional flag to
meta.yaml
.Then wheels need to be uploaded somewhere: maybe an S3 bucket or possibly we could use the same account (different bucket) that is provided for free by Rackspace for the wheels built in MacPython org.
Another point is that conda-press might need to be adapted to work for locally built packages that are not yet uploaded to a conda channel.
The text was updated successfully, but these errors were encountered: