Using citools package instead of bob devtools for the CI process

This is an adaptation to use the citools package instead of bob devtools to process the ci step in a goal to optimize it.

Closes #46 (closed)

assigned to @ydayer

So, the problem may come from scikit-learn itself (https://scikit-learn.org/stable/install.html#installing-on-apple-silicon-m1-hardware):

Installing on Apple Silicon M1 hardware

The recently introduced macos/arm64 platform (sometimes also known as macos/aarch64) requires the open source community to upgrade the build configuration and automation to properly support it. At the time of writing (January 2021), the only way to get a working installation of scikit-learn on this hardware is to install scikit-learn and its dependencies from the conda-forge distribution, for instance using the miniforge installers: https://github.com/conda-forge/miniforge The following issue tracks progress on making it possible to install scikit-learn from PyPI with pip: https://github.com/scikit-learn/scikit-learn/issues/19137

added 1 commit

• ba1e5615 - [ci] Removed unnecessary entry-points

Compare with previous version

added 1 commit

• e5ec76d9 - [ci] Changed package-dir flag to packages

Compare with previous version

Should we temporarily skip the tests part for macOS so we can see if the rest of the pipeline steps (dist, deploy) can finish properly?

You'll then have inconsistent states between what is distributed for Linux and macOS

assigned to @amayoraz and unassigned @ydayer

requested review from @ydayer

added 1 commit

• 45480300 - [ci] (temp) deactivating macOS pipeline

Compare with previous version

added 1 commit

• cd60c9d7 - [ci] use pyproject information for conda

Compare with previous version

added 1 commit

• dc62f999 - [ci] use pyproject information for conda

Compare with previous version

added 1 commit

• 20854db7 - [dist] put package version directly in pyproject.toml

Compare with previous version

added 1 commit

• 940fb342 - [dist] put package version directly in pyproject.toml

Compare with previous version

added 1 commit

• ca043cce - [dist] put package version directly in pyproject.toml

Compare with previous version

added 1 commit

• bf6a292d - [dist] put package version directly in pyproject.toml

Compare with previous version

added 1 commit

• 9302aafb - [dist] add package data

Compare with previous version

Seeing as it prevents the current pipeline from running, do we need to keep the tests and doc building in conda/meta.yaml?

The goal of the deploy step is just to pack the package and push it to the channel/server.

I would assume that tests are already done in previous steps and the conda package does not depend on the doc. This would place every test and doc command in one place: citools.