Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use pip-tools to constrain CI requirements #91

Merged
merged 1 commit into from
Jul 12, 2020

Conversation

pkolbus
Copy link
Contributor

@pkolbus pkolbus commented Jul 12, 2020

In .travis.yml, the versions of coveralls and pytest-cov were unconstrained, creating a risk of failure in Travis CI builds if an incompatible version of pytest-cov or coveralls is released.

As suggested in #89, use pip-tools to address this risk. The dependencies for coverage testing are in requirements-cov.in. The frozen set of packages is in requirements-cov.txt, compiled for
python 2.7.

This is only for coverage testing, since pip-tools doesn't handle relative paths and a minimal environment can help detect undeclared dependencies.

In .travis.yml, the versions of coveralls and pytest-cov were
unconstrained, creating a risk of failure in Travis CI builds if an
incompatible version of pytest-cov or coveralls is released.

As suggested in gforcada#89, use pip-tools to address this risk. The
dependencies for coverage testing are in requirements-cov.in. The
frozen set of packages is in requirements-cov.txt, compiled for
python 2.7.

This is only for coverage testing, since pip-tools doesn't handle
relative paths and a minimal environment can help detect undeclared
dependencies.
@gforcada gforcada merged commit 6aa82a4 into gforcada:master Jul 12, 2020
@gforcada
Copy link
Owner

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants