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

On appveyor, use already installed conda installations? #176

Closed
jankatins opened this issue May 22, 2016 · 9 comments
Closed

On appveyor, use already installed conda installations? #176

jankatins opened this issue May 22, 2016 · 9 comments
Milestone

Comments

@jankatins
Copy link
Contributor

jankatins commented May 22, 2016

See here for a transitioned recipe: matplotlib/matplotlib#6462

See also: appveyor/ci#359 which seens to be the issue implementing it (from https://twitter.com/tacaswell/status/734460129928712192)

@ocefpaf
Copy link
Member

ocefpaf commented May 22, 2016

We already do that in staged-recipes and conda-smithy.

But that is a nice idea to spread to other projects 😉

@ocefpaf ocefpaf closed this as completed May 22, 2016
@jankatins
Copy link
Contributor Author

But why is it still using: https://github.com/conda-forge/conda-smithy/blob/master/conda_smithy/templates/appveyor.yml.tmpl#L49

    - appveyor DownloadFile "https://raw.githubusercontent.com/pelson/Obvious-CI/master/bootstrap-obvious-ci-and-miniconda.py"
    - cmd: python bootstrap-obvious-ci-and-miniconda.py %CONDA_INSTALL_LOCN% %TARGET_ARCH% %CONDA_PY:~0,1% --without-obvci
    - cmd: set PATH=%CONDA_INSTALL_LOCN%;%CONDA_INSTALL_LOCN%\scripts;%PATH%

@ocefpaf ocefpaf reopened this May 22, 2016
@ocefpaf
Copy link
Member

ocefpaf commented May 22, 2016

Right. I missed that part. We should improve the smithy then. Not sure is the bootstrap is downloading or using the local version.

@pelson
Copy link
Member

pelson commented Jun 1, 2016

👍 on doing this. I'd like this to be a coherent part of the simplification we need to do to the feedstocks for 1.0.

@pelson pelson added this to the 1.0 milestone Jun 1, 2016
@jankatins
Copy link
Contributor Author

I just made the experience that updating conda also updates the python in the root env and that update takes ages on appveyor up to the point that I disabled updating conda again (conda/conda#1923 (comment)) . So it might be better to always start with a uptodate conda install...

@jakirkham
Copy link
Member

Already thinking about this, see @jjhelmus and my discussion beginning with this comment.

@pelson pelson mentioned this issue Jul 8, 2016
9 tasks
@jakirkham
Copy link
Member

Though we already have to update python and conda in AppVeyor in staged-recipes and it only takes us a little less than ~2min for that setup w/o building, which includes installing all our dev stuff. See this log. In any event, I don't think it is that bad at conda-forge. Though we do have access to the highest tier on AppVeyor.

I guess the only question is do we want to port over what we are doing at staged-recipes (pretty easy to do) or do we want to hold out for our own Miniconda? Personally I'd be ok porting this code over for the meantime if we are happy with it. Besides there are some Window issues we have to detangle before we can build conda and conda-env.

@jakirkham
Copy link
Member

The code used to do this at staged-recipes is in PR ( conda-forge/staged-recipes#982 ).

@jakirkham
Copy link
Member

Also to reference the installer discussion. Please see issue ( conda-forge/conda-forge.github.io#90 ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants