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

[WIP] Switch to using tox in the CI environment #1238

Closed
wants to merge 1 commit into from

Conversation

mtreinish
Copy link
Member

Summary

This commit switches us to using tox to run tests in the CI environment.
This simplifies our CI environment by first enabling reproducing an
environment exactly like CI locally. The tox command run locally will do
the same thing as CI including setting up an isolated venv for testing.

As part of this the documentation is updated to show how to use tox
instead of the make test target.

Details and comments

@mtreinish
Copy link
Member Author

I'm really looking forward to combining this with #1056 which will make our CI environment basically be a single command with a few env variables set, and we can greatly simplify the travis yaml

@mtreinish mtreinish changed the title Switch to using tox in the CI environment [WIP] Switch to using tox in the CI environment Nov 8, 2018
@diego-plan9
Copy link
Member

Labelling as on hold until after 0.7, as part of the CI discussion.

@diego-plan9 diego-plan9 added the on hold Can not fix yet label Nov 9, 2018
@1ucian0 1ucian0 added this to the 0.8 milestone Nov 23, 2018
@mtreinish mtreinish force-pushed the use-tox-for-ci branch 2 times, most recently from 283ed8b to 9ea4a75 Compare January 8, 2019 22:29
@mtreinish mtreinish removed the on hold Can not fix yet label Jan 8, 2019
This commit switches us to using tox to run tests in the CI environment.
This simplifies our CI environment by first enabling reproducing an
environment exactly like CI locally. The tox command run locally will do
the same thing as CI including setting up an isolated venv for testing.
@diego-plan9 diego-plan9 added the on hold Can not fix yet label Jan 12, 2019
@1ucian0
Copy link
Member

1ucian0 commented Jan 29, 2019

0.7 is out. Let's remove this from on hold.

@1ucian0 1ucian0 added type: qa Issues and PRs that relate to testing and code quality and removed on hold Can not fix yet labels Jan 29, 2019
@diego-plan9
Copy link
Member

Since the main argument seems to be the display benefits, we agreed on discuss them in a separate issue ,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: qa Issues and PRs that relate to testing and code quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants