| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Change-Id: Ie0837a82128536bd9c8cf2fe413e20d4ca3baa73
|
| |
|
|
|
|
|
|
|
| |
PBR is currently creating a pbr.json for any install originating from a
git tree as pbr_json is an entry point for egg_info.writers. If pbr is
not set to True in setup() we now exit before doing any work.
Change-Id: Ia37e37c22c2396f6a10aa2075ea8c501e571fee3
Closes-Bug: 1483067
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Since we don't strip comments from end of the requirements like:
requests-kerberos>=0.6;python_version=='2.7' # MIT
The currnet code ends up failing with a:
"Invalid environment marker"
We should strip the comments out before processing.
Closes-Bug: #1487835
Change-Id: I75d2e83a5f60f93e1c38d53fb4f0a29ba35120b1
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Intended usage, getting a rpm *compatible* version number from pbr
from a pbr using python package. Typically this will then get
put into a rpm spec file (what is used to build an rpm) and used to
build an rpm using `rpmbuild` (the thing used to translate rpm spec
files into rpms).
For example: this allows [1][2] (which I am the primary maintainer of
and godaddy, cray, and y! are users of) to get out of the whacky
and/or flakey rpm version number calculation/conversion process (which
previously just worked around by saying only use tags).
[1] https://github.com/stackforge/anvil
[2] https://anvil.readthedocs.org/en/latest/topics/summary.html
Change-Id: I26cd1d6e8aef69d52e8a4f36bd264c690e712ba3
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
git._iter_log_online() returns None in some cases for instance
when SKIP_WRITE_GIT_CHANGELOG is set to true. This is fixed by
returning an empty list in _iter_log_online.
Also the check if a changelog based on git should be written
was moved from git._iter_log_online to git.write_git_changelog
which makes more sense since some functions were calling
git._iter_log_online to get the changelog for other reasons than
writing it.
Additionally a unittest was added to check that setting the
environment variable SKIP_WRITE_GIT_CHANGELOG to true does not
break anything when retrieving the git version.
Change-Id: Ib12df23ab25b290dd394f9cb1456b8d5da57306a
Closes-Bug: 1467440
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we try to find the git directory, if git is not present, treat
that the same as an error from git itself. Sadly tests for this are
nearly impossible to meaningfully write, since we always have git
installed. I can do a mock based test if folk want one.
Change-Id: If6160d1fb3def8133bdd0b66105e60ef93f80f82
Closes-Bug: #1481468
|
| |/ /
| |
| |
| |
| |
| | |
distribute is long gone.
Change-Id: Id8bf46d997327977e675f3c5e2988827e536d4fd
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The docs for environment markers in setup.cfg [extras] had a
couple of issues.
1) There was a space after the package name.
2) python_environment was used where python_version is the marker.
Change-Id: Idbc72c45ae240356ca39eeba6db754f56c6a0f23
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
readthedocs uses 'setup.py install' to prepare trees for doc creation,
but ChangeLog is not currently created there, and doing so would be
nice. This won't affect develop invocations AFAICT, and even if it
did, the overheads are ~10% of the time to run 0 tests in Nova today -
e.g. quite tolerable.
Change-Id: I7bc18fc9ca2dbe852598cc79b2ad6273fc53557d
|
| | |
| |
| |
| | |
Change-Id: Ic0a09e0ba27e60eecfdcb9eaa589738f97ee8379
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
We get complaints on timing from time to time.
Change-Id: I51bb69f413721197dc37e974b596bae4e8b2bce2
|
| |/ /
| |
| |
| | |
Change-Id: I735058e846783cd0ac361645dc2c0f760d15614e
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As we attempt to get more of OpenStack API servers to be runnable as a
regular WSGI application, we should provide support in PBR for
building these base scripts just like the console scripts.
This adds a new 'wsgi_scripts' group which builds a base script that
will run under mod_wsgi as expected. It also has a CLI fallback mode,
so that the application can be brought up as a wsgiref simple_server
for quick local testing and development. All wsgiref servers default
to binding to port 8000, but that can be overridden.
To support this, and possible future expansion of the script types,
the group list now iterates over a dictionary of group_name =>
template mappings.
This includes basic testing.
It also includes tests which would run an actual wsgi
environment. These are currently skipped as they can't be reliably run
in the gate for timing reasons on stdout processing.
Change-Id: I334639d7ecaad2703d1ff675880a314cc28e2334
|
| | |
| |
| |
| | |
Change-Id: I126133f8fb2e5824188ad4362f18af45734d3f42
|
| | |
| |
| |
| |
| |
| |
| |
| | |
If there are boolean conditions in the env marker, the existing join
causes the extra tag to only be applied to the first of them, causing
carnage.
Change-Id: I7b735befae76b330f923276e1c48ef23816774d4
|
| | |
| |
| |
| | |
Change-Id: If12be720c7057f7014dfb11d4c2a83576cdddfc3
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After digging in pbr and sphinx source code for a day to figure out
what I was doing wrong, let's update the pbr docs with respect to
building docs using the autodoc features in pbr.
Specifically, document the autodoc_tree_excludes and warnerrors
options and point out that you will probably need to set the
exclude_patterns options in your sphinx config when excluding
modules from the docs build and warnerrors=True. Also provide
some links to the Sphinx docs for more details.
Related-Bug: #1260495
Related-Bug: #1472276
Change-Id: Ib43830d08a156f37a3763ad2807d5c1f4cdbe3fe
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Comments are not directly handled by PBR, this documents a reasonable working
set of comments that can be used in setup.cfg.
Comments are parsed out over three locations, configparser, which varies rather
significantly between two and three, pkg_resources, and lastly when pip runs.
Change-Id: Iedebc5baca4e21081708971540d6eab89e043f05
|
| | |/
|/|
| |
| | |
Change-Id: I465ea84f82dfed96c27aeea9337cd28c64c73adf
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Setting env variables with os.environ needs a string as value.
This fixes:
TypeError: must be string, not int
Closes-Bug: #1467880
Change-Id: Ib0c8bbf24f9d4f8926ad71773eb57c3ff41cbec2
|
| | |
| |
| |
| | |
Change-Id: Iaa3699f8db386a39d55e8c2e0605a8edd146546e
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Setuptools doesn't [yet] support markeres in tests_require parameters
to setup(). While we need to get that fixed, we also need to support
syncing marker constrained requirements from global-requirements.
Since version constraints are needed to successfully port to Python3
this won't be a long term viable solution: but few of our test-only
dependencies require version constraints, so we can do this in the
interim. The ones that do - such as python-mysql - we're either
moving away from, or centralising them into optional dependencies
on other packages where the tests_require limitation shouldn't apply.
Change-Id: I31adaf35c8d7b72fe3f8c9242cc356fe34d537e8
|
| |
|
|
|
|
|
|
|
|
|
| |
This caused in issue in the gate for tox -edocs builds:
http://logs.openstack.org/15/187715/5/check/gate-infra-specs-docs/a8cae26/console.html
This reverts commit 1dfe9ef348c777bef67b2c2b1d35e50ebc720333.
Change-Id: Ia6cfbfe5b10a5b714fbb9f21ca61380aaf231638
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
This allows to use patterns such as heat.tests.* to exlude modules from
autodoc genereation.
Change-Id: Ibfc4161670fd9344da88c4a85a3aea992fcdf519
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
Change-Id: Iccb0ba35a008596cb63e1d6954bd9cb8fa50ae78
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Make it obvious to the reader that data_files installation target
location translates to the actual system-wide root filesystem tree
when installed with sufficient permissions to do so.
Change-Id: I67a4dc61ab89b96b4f5e1f99f0199e5a3247412a
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In gnupg 2.1 %no-ask-passphrase is a no-op. As a result gpg attempts to
prompt for a passphrase and as the shell is not interactive it fails.
To allow gnupg 2.1 to create passphrase-less keys we enable two options
new to gnupg 2.1.
%no-protection
%transient-key
Change-Id: If687ff005cf968133fc1fa12b1259a127c464e5b
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This fixture is going to be useful in other places as well.
Change-Id: Ib321db7f9c1a4656fd9dcd583f5893ef9bee3ca7
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The function signature for Sphinx's config.init_values() changed since
version 1.3. That leads to:
TypeError: init_values() takes exactly 2 arguments (1 given)
But the function is already correctly called from
application.Sphinx()'s constructor. So use the configuration object
from the application instead of creating an own config object.
Change-Id: I343c26560bfe5116d5348b50b1890b3442ed845a
Closes-Bug: #1379998
|
| |/ /
| |
| |
| | |
Change-Id: Idd9c01966a5b0f6d6950e9a094b9aeabfc127b44
|
| |\ \ |
|
| | |/
| |
| |
| | |
Change-Id: I033cc482f441d59a193b4b1a87ddcbc96fd99885
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
Change-Id: If9b4db43cd260da731ec5a14599eddedfc33808a
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| | |
testr command is registered by pbr.hooks.commands if
testrepository is installed, so there is no need to
setup the entry point in setup.cfg.
Change-Id: I95aae12d1ac810b6d1d09b71f2a0d87be5ccb6ab
Closes-Bug: #1375048
|
| | |
| |
| |
| |
| |
| |
| |
| | |
pre_run was a method of _PipInstallTestRequires class which was
removed by https://review.openstack.org/#/c/181785/.
Change-Id: I2118f2a96d0c9984797424e5dda47547c8e24621
Closes-Bug: #1456663
|
| |/
|
|
|
|
|
|
|
| |
Get current release of hacking both for new features/rules and to
address a problem where older hacking requires and older version of pbr
than the version of pbr under test. This will get the pep8 jobs working
again for pbr by removing the <1.0 pbr requirement in hacking.
Change-Id: I303db998e3aa64468a931f7e8985592b3446a1c8
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds support for reading extras from setup.cfg.
It also adds support for handling environment markers, both in the
extras section and in install_requires and in requirements.txt.
Change-Id: I6fd8276012e65f82934df9c374613b1ce6856b5a
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
We don't depend on recursive installations via pip - and pip certainly
doesn't support that. We removed part of it recently, finish removing
it all.
Change-Id: I29bc4070b355e52124ceae459ea20403d134b60a
|
| | |
| |
| |
| |
| |
| | |
Node load is too variable.
Change-Id: If03cd577ea18bfad4b53fcddb7a87e48eefe84c1
|
