-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Migrate to Github Actions #71
Conversation
raise NotSupportedError( | ||
'DISTINCT ON fields is not supported by this database backend' | ||
) |
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.
This was failing flake8.
.github/workflows/ci.yml
Outdated
- uses: actions/checkout@v2 | ||
- uses: actions/setup-python@v2 | ||
with: | ||
python-version: 3.6 |
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.
Note that the deploy step used to run on Python 2.7.
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.
Since django-redshift-backend
doesn't create a binary wheel, so I don't think that's a problem.
Not sure why the builds aren't running, but they do run on my fork: https://github.com/browniebroke/django-redshift-backend/actions?query=workflow%3ACI |
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.
LGTM!
Thanks!!
.github/workflows/ci.yml
Outdated
|
||
- name: Publish packages | ||
if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags') | ||
uses: pypa/gh-action-pypi-publish@v1.4.1 |
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 don't know about the Jazzband way of releasing, but I think pypa/gh-action-pypi-publish
with the API provided by PyPI would be better in the future.
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.
@jezdez please check this deploy section. After you agree on the deploy section, we can merge this PR.
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.
This isn't using the Jazzband package index, so will need to update to use it. I'll get to do a proper review later tonight. Don't merge this before.
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 looked at Jazzband's release process and I think I get it... Packages are not published to PyPI directly, they are first going to Jazzband package index which in turns publich to PyPI? I'll copy the publish part from prettytable
, should be a good starting point.
.github/workflows/ci.yml
Outdated
- uses: actions/checkout@v2 | ||
- uses: actions/setup-python@v2 | ||
with: | ||
python-version: 3.6 |
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.
Since django-redshift-backend
doesn't create a binary wheel, so I don't think that's a problem.
.github/workflows/ci.yml
Outdated
|
||
- name: Tox tests | ||
shell: bash | ||
run: tox -e ${{ matrix.versions.tox }} |
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've seen the results of your execution. I think it's perfect 🎉
https://github.com/browniebroke/django-redshift-backend/runs/1364264120
Please use tox-gh-actions for configuring the test matrix instead of duplicating it in the GH actions and tox configuration. This is along the lines we've done with tox-travis. |
a68c17e
to
9e634fd
Compare
9e634fd
to
4522fdd
Compare
Updated test to use Build result: https://github.com/browniebroke/django-redshift-backend/actions/runs/352344702 |
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.
Thanks, this is looking more and more like what we need, thank you for working on this!
A few things that would be better:
da95c9c
to
c1b0b3b
Compare
c1b0b3b
to
6e90872
Compare
I think it's all done. Let me know if I missed anything. |
Is there anything else I need to change here? |
@browniebroke Thank you for your work! @jezdez I'm going to release a new version after merging this PR. What do we need next? |
@jezdez ping and Happy New Year!! |
I've fixed a few more things in #72. Closing this PR since I wasn't able to push to the branch of this PR being in a fork repo. |
Now I've released 2.0.0. Thanks for your contribution! |
Subject: Move CI to Github as Travis builds have become too slow
Feature or Bugfix
Purpose
Move the CI to Github Actions. The config is a bit more verbose than I'd like to, but this should have the advantage to be explicit.
Detail
Relates
I have another PR that will conflict: #68
Given that Travis is too painful to work with, I'll update that other PR when this is merged.
A project admin will have to add
JAZZBAND_RELEASE_KEY
to the repo secrets: https://github.com/jazzband/django-redshift-backend/settings/secrets/actions/new