Commands and tools for building conda packages
Python Batchfile Shell HTML CMake C
Latest commit 65af5bc Jan 20, 2017 @msarahan msarahan changelog 2.1.2
Failed to load latest commit information.
appveyor Windows test fixes: appveyor; dirty args Jun 7, 2016
bin remove remnants of pipbuild Aug 25, 2016
conda.recipe utilize chardet and bs4 to guess file encoding Jan 10, 2017
conda_build Merge pull request #1690 from msarahan/link_error_retry Jan 20, 2017
example_packages more whitespace fixes via autopep8 May 11, 2016
tests Merge pull request #1691 from msarahan/fix_relative_git_url_monkeypatch Jan 20, 2017
.binstar.yml fix VS activation; support VS env var for fiding; Appveyor improvements May 13, 2016
.checkignore add checkignore file to skip versioneer files on quantcode Aug 22, 2016
.codecov.yml add codecov.yml to disable commenting on PRs Aug 21, 2016
.coveragerc omit example skeleton from coverage Aug 21, 2016
.gitattributes add versioneer Jan 17, 2014
.gitignore add .DS_Store to gitignore Jul 8, 2016
.gitmodules more details on necessary external repo Aug 10, 2016
.landscape.yml fixes suggested by Aug 25, 2016
.travis.yml Replace pytest-capturelog by pytest-catchlog during testing Jan 20, 2017
CHANGELOG.txt changelog 2.1.2 Jan 20, 2017
LICENSE.txt Add LICENSE Aug 11, 2014
README.rst document extra package install for testing Nov 28, 2016
appveyor.yml Enable colors for pytest runs on AppVeyor Jan 20, 2017 add exception when SRC_DIR used. Add option to not remove workdir. Warn. Jan 10, 2017
setup.cfg Use [tool:pytest] section name in setup.cfg Jan 20, 2017 remove py34 from Travis. Add filelock in Sep 26, 2016 more whitespace fixes via autopep8 May 11, 2016


conda-build Code issues Code Health


# Display information about current conda install
conda info

# Install conda-build in the current env
conda install -n root conda-build

Building Your Own Packages

You can easily build your own packages for conda, and upload them to, a free service for hosting packages for conda, as well as other package managers. To build a package, create a recipe. See for many example recipes, and for documentation on how to build recipes.

To upload to, create an account. Then, install the anaconda-client and login

$ conda install anaconda-client
$ anaconda login

Then, after you build your recipe

$ conda build <recipe-dir>

you will be prompted to upload to

To add your channel, or the channel of others to conda so that conda install will find and install their packages, run

$ conda config --add channels

(replacing username with the user name of the person whose channel you want to add).


  • `OSError: [Errno 36] File name too long:` - This error has been seen on Linux computers with encrypted folders. The solution is to install miniconda or anaconda to a location that is not encrypted. This error occurs because the encrypted form of the path that conda-build creates can be too long.

Getting Help

The documentation for conda is at You can subscribe to the conda mailing list. The source code and issue tracker for conda are on GitHub.


Contributions to conda-build are always welcome! Please fork the conda/conda-build repository, and submit a PR. If a PR is a work in progress, please put [WIP] in the title. Contributions are expected to pass flake8 and test suites run on Travis CI (linux) and AppVeyor (windows). Contributors also need to have signed our Contributor License Agreement


Running our test suite requires cloning one other repo at the same level as conda-build: - this is necessary for relative path tests outside of conda build's build tree.

Additionally, you need to install a few extra packages:

conda install pytest pytest-cov mock

The test suite runs with py.test. Some useful commands to run select tests, assuming you are in the conda-build root folder:

Run all tests:

py.test tests

Run one test function:

py.test tests/

Run one parameter of one parametrized test function:

Several tests are parametrized, to run some small change, or build several recipe folders. To choose only one of them:

py.test tests/[entry_points]

Note that our tests use py.test fixtures extensively. These sometimes trip up IDE style checkers about unused or redefined variables. These warnings are safe to ignore.