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
Add github build actions #107
Conversation
bc3641e
to
31bf07e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, it's fine. I see one glitch in the step names, but I think it's an upstream bug.
@@ -1,19 +1,19 @@ | |||
venv: | |||
python3 -m venv .venv | |||
python -m venv .venv |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PYTHON ?= python
at the top
then
$(PYTHON)
elsewhere
python3 -m pip install -Ur requirements.txt | ||
python3 -m pip install -Ur requirements-dev.txt | ||
python -m pip install -Ur requirements.txt | ||
python -m pip install -Ur requirements-dev.txt | ||
|
||
dev: venv | ||
source .venv/bin/activate && make setup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PYTHON=.venv/bin/python make setup
.venv/bin/python setup.py develop
?
.github/workflows/build.yml
Outdated
- name: Coverage | ||
continue-on-error: true | ||
run: | | ||
coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this going to update the same location we had with travis?
run: | | ||
python -m pip install --upgrade pip | ||
make setup | ||
pip install -U . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't need the install step if we use PYTHON=.venv/bin/python make test
, etc... up to you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I played with this last night, venv on Windows puts the binaries in a different spot. What you have is fine.
31bf07e
to
5a07600
Compare
Will build on 3.6 and 3.7, on Linux and Mac. Updates makefile to use `python` instead of `python3` because Windows is weird. Windows builds will come later when better support for spawned processes is added.
5a07600
to
f894e32
Compare
Codecov Report
@@ Coverage Diff @@
## master #107 +/- ##
=========================================
Coverage ? 79.15%
=========================================
Files ? 12
Lines ? 801
Branches ? 77
=========================================
Hits ? 634
Misses ? 143
Partials ? 24 Continue to review full report at Codecov.
|
Will build on 3.6 and 3.7, on Linux and Mac. Windows builds will be added once it is fully supported in Bowler, because Github Actions don't currently support the notion of jobs that are allowed to fail. Also drops the Travis CI config and switches to Codecov instead of Coveralls for test coverage reports.