Add simple GithubAction for Tox #9
Conversation
|
We do have CI for that already: |
|
Oh sorry I did not see these. I just saw that you have open pull requests and they are not checked via any CI. So I thought it would be nice to have automatic CI coverage for these. Setting up Github Actions is quite easy to do, so I just gave it a shot. Looking closer the open Pull Requests are also just automatic PRs for security fixes, so no user interaction there I guess... But you could of course also configure your existing Jenkins server to 1) annotate the commits on GitHub with the build results and 2) to also check pull requests. |
|
This job on Green dragon has been spun down AFAICT. I think there's a lot of benefit to setting up automated testing for PRs. @cmatthew What do you think about landing this now? |
|
I'll go ahead and try merging this to see what works and what doesn't. I think there's a lot of value in having automated testing immediately in Github PRs and the free tier machines should be way sufficient for our needs. |
3 participants
The low-hanging fruit for automatic checks is probably getting tox executed on Github Actions.
I was able to run
flake8,mypyanddocssuccessfully.However I failed with the test suite. We probably need to set up some more things in the environment...
The output of the Github Actions is visible here: https://github.com/ChristianKuehnel/llvm-lnt/actions