-
Notifications
You must be signed in to change notification settings - Fork 67
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
New test CI attempting to use Github Actions #2837
Conversation
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
06b3082
to
9f029db
Compare
All green after 5h of CPU time 🎉 |
Signed-off-by: Jean Privat <[email protected]>
Signed-off-by: Jean Privat <[email protected]>
Ok, I played more with the CI to solve the forked repo issue.
This also have the advantage of having a single big report instead of a small one per job. The main drawback (for now) is that while the PR provide both workflow, only the PR one is run as the master one is not installed (yet). It will be once (if) the PR is merged. |
The script we used and that linked github repo and gitlab CI is broken, thanks to changes in both web api.
As maintaining this script is cumbersome, another option is to use Gitub Action that might be now more mature and usable in production.
This PR thus introduces a complete CI workflow with basic tests and a full matrix check.
All tests should run and be green, including weird ones that require neo4j, mongodb or various third parties libraries.
The main changes are:
pug
used in a few popcorn tests (2, the lowest value of few)