devpi-builder 2.3.0

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:

progressbar==0.2.2
progressbar==0.2.1
PyYAML==3.11

Commandline Usage

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

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

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.
  --run-id RUN_ID       Add the given string to all entries in the XML output,
                        allowing to distinguish output from multiple runs in a
                        merged XML.
  --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
                        server.

Features

• 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.

License

New BSD

Version 2.3.0 — 2017-04-07

Version 2.2.0 — 2016-05-23

Added

• Capture build errors for better output in case of build failures. Thanks Travis Mehlinger.

Version 2.1.0 — 2016-04-22

Added

• Support for client certificates. Thanks Hans Lawrenz.

Version 2.0.0 — 2016-01-20

Version 1.0.0 — 2015-05-22

Changed

• Use devpi-plumber instead of a custom devpi wrapper.

• Check the blacklist first when deciding whether to build a package.

Version 0.4.0 — 2015-09-13

Version 0.3.0 — 2015-08-15

Added

• Support for special-case handling of pure python wheels

• Optional support for reporting skipped packages in a JUnit-compatible XML

• Python 3 support

Version 0.2.1 — 2014-08-07

Fixed

• Fixed crash if a built wheel could cannot be found (because pip<=1.5.2 skipped it).

Version 0.2.0 — 2014-08-01

Version 0.1.0 — 2014-08-01

Added

• Build a list of packages and upload them to a Devpi index