Automatically build and upload python packages to devpi
Latest commit 0a8a999 Dec 19, 2016 @theMarix theMarix committed on GitHub Merge pull request #100 from HolgerPeters/master
Migrate to pytest


Brandon the Devpi Builder

Build Status Coverage Status Latest Version Requirements Status

Brandon, the devpi builder, takes a requirements.txt and incrementally fills a devpi index with wheels of the listed python packages.

Brandon by Example

Given a requirements.txt, we can upload all listed packages to the index opensource/Debian_7 on a local devpi using the following command:

$ devpi-builder requirements.txt http://localhost:3141/opensource/Debian_7 opensource mypassword

Example of such a requirements.txt:


Commandline Usage

usage: devpi-builder [-h] [--blacklist BLACKLIST] [--pure-index PURE_INDEX]
                     [--junit-xml JUNIT_XML] [--dry-run]
                     [--client-cert CLIENT_CERT]
                     requirements index user password

Create wheels for all given project versions and upload them to the given

positional arguments:
  requirements          requirements.txt style file specifying which project
                        versions to package.
  index                 The index to upload the packaged software to.
  user                  The user to log in as.
  password              Password of the user.

optional arguments:
  -h, --help            show this help message and exit
  --blacklist BLACKLIST
                        Packages matched by this requirements.txt style file
                        will never be build.
  --pure-index PURE_INDEX
                        The index to use for pure packages. Any non-pure
                        package will be uploaded to the index given as
                        positional argument. Packages already found in the
                        pure index will not be built, either.
  --junit-xml JUNIT_XML
                        Write information about the build success / failure to
                        a JUnit-compatible XML file.
  --dry-run             Build missing wheels, but do not modify the state of
                        the devpi server.
  --client-cert CLIENT_CERT
                        Client key to use to authenticate with the devpi


  • Read a requirements.txt style input file.
  • Support multiple versions of a package in the same file
  • Only build packages not yet in the target index.
  • Support a black-list for packages to never be built and uploaded (certain packages like numpy are fragile regarding their interdependency with other packages).
  • Can use separate indices for plain python packages and those with binary contents.
  • Can log build results to a JUnit compatible XML file, thus that it can be parsed by Jenkins.