-
Notifications
You must be signed in to change notification settings - Fork 19
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
tests: Run integration test in GitHub actions #35
Conversation
d6ffbdd
to
9b180bc
Compare
I also ran this on my fork in combination with the extra tests from PR #34. You can see the result in this run. |
Run them on pull requests, and every Monday morning, to catch regressions in operating systems and outside dependencies.
9b180bc
to
ec65d9b
Compare
Sorry for the blocked setting/unsetting -- it pretty well does not matter which one (this or #34) lands first, the other one then needs to be rebased, to make sure that the new checks work in github actions. |
Why not do the ubuntu test runs for every PR? That is, why only once per week? |
[citest pending] |
It does run for every PR -- you can already see the result right here in the tests. It has two triggers, "on: pull" and "on: cron". |
[citest pending] |
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
Run them on pull requests, and every Monday morning, to catch
regressions in operating systems and outside dependencies.
This provides feedback for role changes on at least one operating system for outside contributors like me, where the integration tests don't run automatically. It may also help you to remove some of your own custom infra.
If you generally like this, I am happy to work on this some more, and run the test in containers instead (system containers with systemd ought to work well enough these days). Then we can have a test matrix for debian, ubuntu, centos, fedora, and possibly even UBI.