Dear all, Contrib projects template hints the authors to use TravisCI, CircleCI and Appveyor. Now that CircleCI has moved to version 2, is there any idea on what to do about it? Will the template be updated? Is it ok if we use only CircleCI? What do you, core devs, suggest about that? Best wishes Manuel
Hi Manuel, Basically, you are free to take any initiative with your CIs until it is cross-platform tested. Using the different CI available allows to speed-up the testing. In scikit-learn, we use Travis for Linux checking, Appveyor for Windows, and CircleCI for building the documentation. You could use a single CI service for all of those. However, I am not sure that you have Windows support apart of Appveyor. I think that we should update the template of the scikit-learn-contrib with the new template for circle ci 2. Cheers, On Thu, 6 Sep 2018 at 13:16, Manuel CASTEJÓN LIMAS via scikit-learn <scikit-learn@python.org> wrote:
Dear all, Contrib projects template hints the authors to use TravisCI, CircleCI and Appveyor. Now that CircleCI has moved to version 2, is there any idea on what to do about it? Will the template be updated? Is it ok if we use only CircleCI? What do you, core devs, suggest about that? Best wishes Manuel _______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
-- Guillaume Lemaitre INRIA Saclay - Parietal team Center for Data Science Paris-Saclay https://glemaitre.github.io/
Thank you for your feedback Guillaume! I'm fighting with CircleCI configuration yet, but it seems it will be possible to test the windows versions as well, provided that nowadays we already have windows containers available. I'll give it a try and then I will share the experience. For what I've seen in scikit-learn build_tools scripts, there is room for speeding up things by integrating the miniconda installation in the docker image and not on every build job. Best Manuel El jue., 6 sept. 2018 a las 14:24, Guillaume Lemaître (< g.lemaitre58@gmail.com>) escribió:
Hi Manuel,
Basically, you are free to take any initiative with your CIs until it is cross-platform tested. Using the different CI available allows to speed-up the testing. In scikit-learn, we use Travis for Linux checking, Appveyor for Windows, and CircleCI for building the documentation. You could use a single CI service for all of those. However, I am not sure that you have Windows support apart of Appveyor.
I think that we should update the template of the scikit-learn-contrib with the new template for circle ci 2.
Cheers, On Thu, 6 Sep 2018 at 13:16, Manuel CASTEJÓN LIMAS via scikit-learn <scikit-learn@python.org> wrote:
Dear all, Contrib projects template hints the authors to use TravisCI, CircleCI
and Appveyor. Now that CircleCI has moved to version 2, is there any idea on what to do about it? Will the template be updated? Is it ok if we use only CircleCI?
What do you, core devs, suggest about that? Best wishes Manuel _______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
-- Guillaume Lemaitre INRIA Saclay - Parietal team Center for Data Science Paris-Saclay https://glemaitre.github.io/ _______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
participants (3)
-
Guillaume Lemaître -
Manuel Castejón Limas -
Manuel CASTEJÓN LIMAS