Use GitHub Actions for CI #1051
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also: - Start to try to use GitHub Actions to do continuous integration testing - Reduce number of TravisCI builds to see if it helps with how god awfully long it takes
Also: - Refactored do_history command to extract a helper method to fix a flake8 warning about high complexity
Also: - Install setuptools and setuptools-scm to hopefully help with version confusion due to lack of setuptools-scm - Try running nox using python -m since it wasn't found as a command when running on windows via GitHub Actions
…ons not being able to determine version via setuptools_scm
…ebhook within GitHub settings for the repo
Codecov Report
@@ Coverage Diff @@
## master #1051 +/- ##
==========================================
+ Coverage 96.78% 98.14% +1.36%
==========================================
Files 21 22 +1
Lines 4597 4630 +33
==========================================
+ Hits 4449 4544 +95
+ Misses 148 86 -62
Continue to review full report at Codecov.
|
This switches from using a conda-based Windows environment on AppVeyor to a default one. The purpose is to see if we can significantly speed up tests running on AppVeyor. Because if we can't, then I am just going to remove use of AppVeyor entirely in favor of GitHub Actions.
Also tried to fix AppVeyor build
…han GitHub Actions for the same purpose
…tions matrix Also: - Temporarily disable dependency caching in GitHub Actions - For Azure Pipelines MacOs testing, add Python 3.9 and remove 3.5
…in GitHub Actions yet
Also: - Move flake8 linting to its own workflow - Add new workflow for Sphinx documentation build
|
This PR is now ready for review. |
…R instead of only ones to specific branches I like getting to see the output of CI tools while I develop on a branch and suspect that will be handy for others as well.
…sn't used any longer
This was referenced Jan 31, 2021
anselor
approved these changes
Jan 31, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use GitHub Actions for continuous integration (CI) testing on Linux, macOS, and Windows
Also:
do_historycommand slightly to fix aflake8warning about high complexityFixes #874
This PR replaces all of Travis CI (Linux) and AppVeyor (Windows) for testing with GitHub Actions. For now, Azure Pipelines has been left in place for MacOS testing even though this is redundant with the GitHub Actions configuration.
TODO:
setuptools_scmversion working correctlynoxflake8linting to a separate workflow