Update cffi from 1.12.2 to 1.12.3
Update cffi from 1.12.2 to 1.12.3
Update configparser from 3.7.4 to 4.0.2
Update cryptography from 2.6.1 to 2.7
Update cryptography from 2.6.1 to 2.7
Update gitpython from 2.1.11 to 3.0.2
Update isort from 4.3.17 to 4.3.21
Update lazy-object-proxy from 1.3.1 to 1.4.2
Update pbr from 5.1.3 to 5.4.3
Update pluggy from 0.9.0 to 0.13.0
Update pyyaml from 5.1 to 5.1.2
Update requests from 2.21.0 to 2.22.0
Update requests from 2.21.0 to 2.22.0
Update stevedore from 1.30.1 to 1.31.0
Update tox from 3.8.6 to 3.14.0
Update virtualenv from 16.4.3 to 16.7.5
Update wrapt from 1.11.1 to 1.11.2
Update certifi from 2019.3.9 to 2019.9.11
Update urllib3 from 1.24.2 to 1.25.3
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
TUF specific schemas have moved to tuf.formats, ensure they are used
throughout and remove stray references to no longer supported schemas
in securesystemslib.format
Signed-off-by: Joshua Lock <jlock@vmware.com>
Removal of securesystemslib exceptions that are TUF-specific
occurs in securesystemslib PR #165https://github.com/secure-systems-lab/securesystemslib/pull/165
This commit adapts to those changes. Exceptions that are specific
to TUF should be in TUF and not in securesystemslib. This commit
uses those already-existing TUF exceptions instead of pointing to
securesystemslib exceptions that will be removed.
For example, securesystemslib has no notion of repositories, so
it's ridiculous to have a RepositoryError in securesystemslib and
ridiculous for TUF to use
securesystemslib.exceptions.RepositoryError.
Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
Re-generate metadata to adopt spec version format change, using
`generate_project_data.py`:
```
cd tests/repository_data && rm -rf project
python generate_project_data.py
```
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Updates SPEC_VERSION definition in tuf/__init__.py, test files and
docstring in formats.build_dict_conforming_to_schema.
Test metadata will be updated in separate commits.
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Add schemas KEYDB_SCHEMA, SIGNATURESTATUS_SCHEMA and
VERSIONINFO_SCHEMA, removed in
secure-systems-lab/securesystemslib#165 as TUF specific, and adopt
usage accordingly.
NOTE: The usefulness of these schemas may be assessed in a
different PR.
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
The function used to last be implemented in securesystemslib
and repository_lib.get_taget_hash only served as wrapper.
secure-systems-lab/securesystemslib#165 drops the function as
TUF-specific.
The used constant `securesystemslib.util.HASH_FUNCTION`
is replaced with `tuf.settings.DEFAULT_HASH_ALGORITHM`, both of
which default to 'sha256'.
NOTE: repository_lib.get_taget_hash might be removed altogether in
the future (see corresponding code comment).
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Coverage used to be configured to omit certain directories while
reporting.
This commit slightly optimizes coverage to already omit those
directories while measuring coverage.
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
This commit partially reverts the workaround introduced by
157167e0cc. Instead of patching the
path, we configure tox to install TUF in editable mode, which makes
the tests run against the same files as if the path were patched.
This makes it so that coverage records paths that it can then
normalize when sending them to coveralls.io (see .travis.yml).
See af22701140
for detailed background information.
As a consequence we can now skip building of sdist and installing it
into a virtual env directory in tox.
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
This replicates behavior of unittest's `discover` method, and
allows `coverage` and the tool that posts coverage reports to
coveralls.io, i.e. `coveralls`, to record the correct paths and
left-strip the parts leading to the project directory.
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
We install coverage inside tox builds to generate test coverage
reports. These reports need to be created with a version supported
by coveralls, which we use (outside of tox) to publish coverage
reports to coveralls.io.
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
- Add a build matrix to run each tox env in a corresponding
travis env as per travis/tox best practices.
https://docs.travis-ci.com/user/languages/python/#using-tox-as-the-build-script
- Add Python 3.5 tests
- Remove only build on certain branch restrictions
- Use "install" instead of "before_script" to install dependencies.
Explicitly listing "install" prevents Travis from automatically
running `pip install -r requirements.txt`, which is not necessary
because most of those requirements are installed again in each
tox environment.
- Move pylint and bandit calls to tox (pylint requires
dependencies) to be installed.
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Coveralls is used to publish coverage results online via
coveralls.io.
Travis is already configured to run it "after_success", but this
has failed for a while, because it was not installed.
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
