requirements/tools
Tony Breeds bf3ce4dc03 [tools/grep-all.sh] Get branches from git
Rather than hard code the branches to look at just do all the stable
branches that exist.

Change-Id: I8beb6ed5e537f37e707d1e04ad9c1174fd608544
2017-09-28 12:42:27 +10:00
..
babel-test.sh Babel Integration tests 2016-04-24 17:21:18 -05:00
build_wheels.sh Add a bashate tox environment and address errors 2017-09-28 12:09:04 +10:00
cap.py Fix "wrap functions with 2 blank lines" pep8 check 2016-11-16 18:52:03 +08:00
check-install.py Fix "wrap functions with 2 blank lines" pep8 check 2016-11-16 18:52:03 +08:00
cruft.sh Add semi-colon as separator for parsing package names 2016-05-06 16:05:17 -04:00
grep-all.sh [tools/grep-all.sh] Get branches from git 2017-09-28 12:42:27 +10:00
integration.sh Use python3 to calculate freezes 2016-09-06 03:34:23 +00:00
publish_constraints.sh Add a bashate tox environment and address errors 2017-09-28 12:09:04 +10:00
README.txt Add a tool to generate the upper-constraints.txt file for publishing 2017-09-27 09:14:04 +10:00
what-broke.py Fix typo in what-broke.py 2016-12-19 07:13:35 +00:00

OpenStack Requirements tools.

This directory contains a number of tools that are useful to the requirements core team and OpenStack
developers.

babel-test.sh
-------------
A tool check for regressions with new Babel releases.

build_wheels.sh
---------------

Generate wheels for all of the requirements, ignoring any packages
that won't build wheels so we get as many as possible. This is meant
to be used on a development box combined with devpi and a wheelhouse
configuration setting for pip, such as described in
https://www.berrange.com/posts/2014/11/14/faster-rebuilds-for-python-virtualenv-trees/

cap.py
------

Take the output of 'pip freeze' and use the installed versions to caps requirements.

check-install.py
----------------

Used in tox environment pip-install.  Only installs requirements (as opposed to
test-requirements and verifies that all console-scripts have all modules
needed.

cruft.sh
--------

This script, when run from the root directory of this repository, will search
the default and feature branches of all projects listed in the projects.txt
file for declared dependencies, then output a list of any entries in the
global-requirements.txt file which are not actual dependencies of those
projects. Old dependencies which were removed from projects or which were used
only for projects which have since been removed should be cleaned up, but many
entries likely represent recent additions which still have pending changes to
add them to one or more projects. In most cases, git pickaxe will yield the
answer.

grep-all.sh
-----------

List a requirements specification and constratint for a given libarary

integration.sh
--------------

Used in the gate!  Install all the "$PROJECTS" to verify that g-r and the each project are compatible

publish_constraints.sh
----------------------
Used in the gate!  Generate the constraints files from git for publishing to a
static server.

what-broke.py
-------------
figure out what requirements change likely broke us.