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

Setup continuous integration #13

Open
spencerahill opened this issue Jun 29, 2020 · 0 comments
Open

Setup continuous integration #13

spencerahill opened this issue Jun 29, 2020 · 0 comments

Comments

@spencerahill
Copy link
Member

CI helps make sure that we never accidentally break something when we merge in new code. At the very least, it checks that the package can be installed on all of the different python versions and platforms (Windows/Mac/Linux) that we choose to support.

But ultimately it will also run our full suite of unit tests, once we create that, to check not only that the install works but also that all of our tests run and pass on all python versions/platforms.

We can+should also configure it with a linter to make sure that all code adheres to standard style and formatting rules. E.g. flake8.

Azure Pipelines is a good option, see e.g. https://github.com/spencerahill/aospy/tree/master/ci. It takes some configuring to get all working, which is true of any CI tool, but it's well worth it.

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

No branches or pull requests

1 participant