Tooling & data
These components do not necessarily perform automation actions on their own (e.g. they don't change the state of a feedstock or a package). Instead, they support other components in conda-forge's infrastructure.
conda-smithyโ
- ๐ Source at
conda-forge/conda-smithy - ๐ฆ Packaged at
conda-forge/conda-smithy-feedstock - ๐ Documentation
This is the main feedstock creation and maintenance tool.
Most of its usage is automated by our infrastructure:
- Feedstock creation and services registration at
staged-recipes - Regeneration (rerendering), linting and hinting in PRs done by
conda-forge-linteronwebservices
However, you can also use it locally or on your forge-like deployments. For local debugging, you will find these commands useful:
conda-smithy rerenderconda-smithy recipe-lint
conda-forge-pinningโ
- โ๏ธ Deployed in Anaconda.org via
conda-forge/conda-forge-pinning-feedstock - ๐ Has access to Azure, Anaconda.org (cf-staging)
Hosts the global pinnings for conda-forge, and the ongoing migrations.
conda-forge-repodata-patchesโ
- โ๏ธ Deployed in Anaconda.org via
conda-forge/conda-forge-repodata-patches - ๐ Has access to Azure, Anaconda.org (cf-staging)
This repository creates the repodata.json patches used by the Anaconda.org to amend the metadata coming from the published packages.
Read more bout this in The package life cycle.
conda-forge-ci-setupโ
- โ๏ธ Deployed in Anaconda.org via
conda-forge/conda-forge-pinning-feedstock - ๐ Has access to Azure, Anaconda.org (cf-staging)
This special feedstock provides a package that defines the logic to install and configure a common CI setup across providers.
docker-imagesโ
- โ๏ธ Deployed in
conda-forge/docker-images - ๐ Has access to DockerHub and Quay.io
- โ Needed by
staged-recipes, feedstocks.
This repository builds the Docker images used to provide a unified system on all Linux builds.
regro/cf-scriptsโ
- ๐ Source at
regro/cf-scripts - ๐ Documentation
The code and logic behind autotick-bot.
regro/cf-graph-countyfairโ
- โ๏ธ Deployed in Github Actions via
regro/cf-graph-countyfair - โ Needs
regro/cf-scripts,conda-forge/conda-forge-pinning-feedstock - ๐ค Uses
@regro-cf-autotick-bot - ๐ Has access to Github API
This is the graph data used by autotick-bot.
The logic to build the graph is provided by cf-scripts.
regro/libcfgraphโ
- โ๏ธ Deployed in Circle CI via
regro/libcfgraph - โ Needs
regro/libcflib - ๐ค Commits as
circleci(fake username) - ๐ Has access to Github API, Circle CI
The libcfgraph data is similar to cf-graph-countyfair.
regro/libcflibโ
- ๐ Source at
regro/libcflib - ๐ฆ Packaged at
conda-forge/libcflib-feedstock - ๐ Not documented
This is the code that builds the data served at libcfgraph.
feedstocks monorepoโ
- โ๏ธ Deployed in
conda-forge/feedstocks
A single repository containing all feedstocks as submodules.
feedstock-outputsโ
- โ๏ธ Deployed in Github Actions via
conda-forge/feedstock-outputs - ๐ Has access to Azure, Anaconda.org (cf-staging)
This repository is a registry of feedstock names and the packages (artifacts) they produce.
Its main purpose is to provide an allow-list for the validation server to prevent malicious cross-feedstock builds, although it's also an informative map of feedstocks <-> packages that is exposed in the packages section of the website.
Othersโ
regro/conda-suggest-conda-forgeprovidesconda-suggestfiles that map executables to package names.