Utilities for projects using pbr
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Andreas Jaeger 2202ec699b Fix playbooks/container-images/pre.yaml after OpenDev 1 month ago
doc/source Add documentation about build-images 10 months ago
pbrx Run an sdist before the bdist_wheel command 7 months ago
playbooks/container-images Fix playbooks/container-images/pre.yaml after OpenDev 1 month ago
releasenotes Implement basic image push 9 months ago
tools Correct small typo 8 months ago
.coveragerc Initial Cookiecutter Commit 1 year ago
.gitignore Initial Cookiecutter Commit 1 year ago
.gitreview OpenDev Migration Patch 1 month ago
.mailmap Initial Cookiecutter Commit 1 year ago
.stestr.conf Initial Cookiecutter Commit 1 year ago
.zuul.yaml Remove container build jobs 3 months ago
CONTRIBUTING.rst Initial Cookiecutter Commit 1 year ago
HACKING.rst Initial Cookiecutter Commit 1 year ago
LICENSE Initial Cookiecutter Commit 1 year ago
README.rst Add documentation about build-images 10 months ago
babel.cfg Initial Cookiecutter Commit 1 year ago
requirements.txt Add support for building container images from pbr source 1 year ago
setup.cfg Remove python2 10 months ago
setup.py Initial Cookiecutter Commit 1 year ago
test-requirements.txt Initial Cookiecutter Commit 1 year ago
tox.ini Merge "fix tox python3 overrides" 10 months ago

README.rst

pbrx

Utilities for projects using pbr.

pbr is very opinionated about how things should be done. As a result, there are a set of actions that become easy to deal with generically for any pbr based project. pbrx is a collection of utilities that contain support for such actions.

Note

Each of the utilities has a primary focus of working for projects using pbr. However, some of them will also work just fine for non-pbr-based projects. When that is the case, the utility will be marked appropriately.

Features

Each utility is implemented as a subcommand on the pbrx command.

install-siblings

Updates an installation with local from-source versions of dependencies. For any dependency that the normal installation installed from pip/PyPI, install-siblings will look for an adjacent git repository that provides the same package. If one exists, the source version will be installed to replace the released version. This is done in such a way that any given constraints will be honored and not get messed up by transitive depends.

build-images

Builds container images from a project's source tree. The python:alpine base image is used, and dependencies are taken from bindep.txt for distro requirements and requirements.txt for python requirements. A base image is made for the project itself, and then an additional image based on the base image for every entry in entry_points.console_scripts in the setup.cfg file.