-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Run CI on Github actions #7654
Run CI on Github actions #7654
Conversation
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.
Not sure why it doesn't run now — maybe because it's a third party PR, but let's merge and see what happens. |
Running great — took just 49s for the uncached job! https://github.com/Leaflet/Leaflet/runs/3525418592 |
@mourner Nice, that is a lot faster than I expected! |
It looks like the tests only ran on PhantomJS though, I guess that is not entirely correct considering the browser parameters passed in. This might be related to my changes to the scripts in the package. I'll open up a separate PR to debug this, hopefully that will just run the task now that an initial version was merged. |
Depends on #7653 as a
package-lock.json
file is needed to runnpm ci
. Allows running the CI on Github actions instead of Travis, as it looks like the Travis builds are not running. Added benefit is that forks can use the same configuration to run CI without having to set up Travis and change the source.