Organization GuideΒΆ

For organizations, it is recommanded to fork this repository and to adapt the config.bat file in which you should give:

  • Conda channels used for builds and installs,
  • Anaconda label used for uploads.

For example, let us consider the config.bat written for the StatisKit organization:

  1. The TEST_LEVEL environment variables is used in Conda recipes to control the test launched (e.g., code:1 is for unit tests).

  2. The r Conda channels is added for all repositories.

  3. Uploads made on the release label of the Anaconda statiskit channel are only allowed for master branches. Otherwise, the label is changed to develop.

  4. develop and release are the only accepted labels for uploads made on the Anaconda statiskit channel.

  5. For uploads on:

    • Another Anaconda channel than statiskit, the channels used by Conda are statiskit (with the main label and develop labels) and the one given by the code:ANACONDA_OWNER environment variable (with the main and the label given by the ANACONDA_LABEL environment variable if given).

    • The statiskit Anaconda channel, the channel used by Conda is statiskit (with the main label and the label given by the ANACONDA_LABEL environment variable if given).

      Note

      In order to prevent Anaconda channel collision for the release label on the statiskit channel (e.g. with AppVeyor CI), the release label is changed to appveyor-release.