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

ci: Replace Travis with GitHub workflow #188

Merged
merged 3 commits into from
Dec 11, 2020

Conversation

manics
Copy link
Member

@manics manics commented Dec 11, 2020

See jupyterhub/team-compass#353

This is based on https://github.com/jupyterhub/oauthenticator/tree/be91e7d9e58f13221615a64a506529c775abe593/.github/workflows

The main changes from the Travis configuration are:

  • Added Python 3.9
  • Removed Python nightly
  • Pypi publishing of tags is independent of test status

@manics manics requested a review from consideRatio December 11, 2020 13:10
@manics
Copy link
Member Author

manics commented Dec 11, 2020

This will require PyPI secrets to be setup

@consideRatio
Copy link
Member

consideRatio commented Dec 11, 2020

This LGTM

I'm conflicted about having the test build part of the release workflow as it feels misleading to run a test there, but i'm aware that it would lead to breaking of DRY if we had a dedicated test in the test workflow which isnt great either.

We can't overwork this with our limited maintenance time though and it will be a compromise no matter what and its not sure my preference is most sensible.

If you are ready, lets merge! The pypi password is already setup ahead of time for this repo!

@consideRatio consideRatio merged commit e55cdef into jupyterhub:master Dec 11, 2020
@manics manics deleted the github-workflow branch December 11, 2020 18:54
@consideRatio consideRatio changed the title Replace Travis with GitHub workflow ci: Replace Travis with GitHub workflow May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants