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

Replace Travis with GitHub Actions #350

Closed
wants to merge 2 commits into from
Closed

Replace Travis with GitHub Actions #350

wants to merge 2 commits into from

Conversation

ajcerejeira
Copy link

@ajcerejeira ajcerejeira commented Sep 21, 2020

Hello!

Now that Github introduced actions we could replace .travis.yml configuration, having a more integrated workflow for the testing and deployment pipelines.

I created this PR that includes a GH action that does the same steps as Travis: building the package for a matrix of different systems (ubuntu and macos for each Python version between 3.5 and 3.6), configuring and installing Miniconda, deploying to PyPI on tags, linting the code and building the docs.

You can see an example of this actions running on my fork, here:
https:/ajcerejeira/nox/actions/runs/265352396

I tried to make the pipeline also work for windows, but I was not able to run the tests (building and installing the packages worked fine), perhaps I should look into the appveyor.yml file and try to replicate that?

If this PR is accepted the repository owner should add PYPI_PASSWORD to this repository secret settings, like explained here:
https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

Thank you all, and have a nice day :)

Close #368

@richin13
Copy link

richin13 commented Dec 1, 2020

Linking #368

@dhermes dhermes changed the title Replace Travis with Github Actions Replace Travis with GitHub Actions Dec 1, 2020
Copy link
Collaborator

@stsewd stsewd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks this looks good! We should include python 3.9 as well and remove 3.5.

https:/theacodes/nox/blob/4e1842246d8b005e0dadf4b0f3e9d1123cefa651/setup.py#L37-L41

I think is fine to keep using appveyor for windows.

.github/workflows/ci.yml Outdated Show resolved Hide resolved
Copy link
Collaborator

@stsewd stsewd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks! I'll leave to @theacodes to merge this, since she needs to set the PYPI_API_TOKEN.

.github/workflows/ci.yml Outdated Show resolved Hide resolved
@theacodes
Copy link
Collaborator

The secret's been added. @stsewd I'm also happy to grant you PyPI permissions.

Feel free to merge once the suggestion is accepted.

@stsewd
Copy link
Collaborator

stsewd commented Dec 28, 2020

@theacodes thanks! I already have permission on pypi, just wasn't able to create secrets in the repo

Setup a Github Action configuration file that runs the same steps as the
Travis setup, i.e, building, testing, linting and building documentation
for Ubuntu and MacOS systems for each Python version between 3.5 and
3.7.

It uses
[miniconda action](https:/marketplace/actions/setup-miniconda)
to install and configure miniconda, and
[PyPI publish](https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/)
action to deploy the package to PyPI.
Base automatically changed from master to main February 11, 2021 23:24
@theacodes
Copy link
Collaborator

Superseded by #389

@theacodes theacodes closed this Feb 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Migrate from travis-ci
4 participants