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
packaging and CI refactor #23
Conversation
In order to use CircleCI, an owner on this repo will need to go here and allow the project to be tested: https://circleci.com/gh/airbrake/airbrake-python |
👍 |
@kyrylo Any chance you could have someone from the team review? Been waiting on a merge for this for a while. Thanks! |
Hey! Thanks for the reminder. Never hesitate to ping, you are always welcome :) We'll review this ASAP (which is probably tomorrow or during this week). |
@kyrylo If you are cool with testing in CircleCI, an owner will need to go here and choose to "follow" the project: https://circleci.com/gh/airbrake/airbrake-python |
@samstav 👍 on the tox + circleci additions. LGTM @kyrylo LGTM. @vmihailenco want to give this a one over when you have a moment? |
I think I enabled CircleCI, but it fails https://circleci.com/gh/airbrake/airbrake-python/1 |
That's our preferred way! :) |
Looks like its circle trying to infer how to run tests. Will work with @samstav to try to get things going more as intended. Thanks getting the ball rolling. |
CI is happy now: https://circleci.com/gh/samstav/airbrake-python/16 |
Among other things, this change adds a
circle.yml
file so we can start testing airbrake-python using CircleCI which is free for open source projects like this one.The python versions I have configured for testing are:
I have a passing CircleCI build on my fork against the code in this pull request: https://circleci.com/gh/samstav/airbrake-python/12