Build: Migrate CI to GitHub Actions

[ygj6]

Summary

Migrate CI to Github Action.

• Add node.js.yaml to support github action.

• Modify Gruntfile.js to support running travis and github actions at the same time.

Checklist

• All authors have signed the CLA at https://cla.js.foundation/jquery/jquery
• New tests have been added to show the fix or feature works
• Grunt build and unit tests pass locally with these changes
• If needed, a docs issue/PR was created at https://github.com/jquery/api.jquery.com

[mgol]

Wow, this is so awesome, thanks a lot! We planned to migrate from Travis to GitHub Actions for quite some time.

I'll have a closer look this week.

The next step that we planned (to be done later) was to start testing on real browsers on GitHub Actions using our BrowserStack account, phasing out our TestSwarm usage. I was thinking about making it easy to restart runs only in some browsers if they're flaky. One advantage of TestSwarm is we're able to restart a test run of any module in any browser and leave the rest intact; it'd be great to have something like that here.

It'd also be great to have a pipeline graph view, where we're doing the full build only once and then split that to browser testing for each browser. Something like what Blue Ocean provides for Jenkins.

If you have any thoughts on the above that, I'm all ears.

In any case, thanks again for making a very important first step. 👏

[ygj6]

Hi, mgol
Thanks for your review.

I'm considering switch to Browerstack in other PR and keep this PR simply using Github Actions.
Is it Ok for you?

[mgol]

I'm considering switch to Browerstack in other PR and keep this PR simply using Github Actions.
Is it Ok for you?

Yes, definitely!

[mgol]

One thing that makes me worry a bit is missing support for re-running a single job. This is key to us; as we start testing on browsers, we need to be able to only re-run what failed instead of everything which creates a risk of yet another failure. See this thread: https://github.community/t/ability-to-rerun-just-a-single-job-in-a-workflow/17234

[mgol]

This feature missing makes me think we might want to try CircleCI with its visual workflows instead: https://circleci.com/docs/2.0/workflows/

[ygj6]

One thing that makes me worry a bit is missing support for re-running a single job.

Currently, gh-action is becoming more and more popular, the community should have plans to provide this feature .

In fact, jQuery build time is not long, maybe switching to gh-action is a good choice, what do you think?

[ygj6]

I was thinking about making it easy to restart runs only in some browsers if they're flaky

As far as I known, we can get BrowserStack's report by karma. So we can parse the report to get the failed browsers and rerun the failed browsers in the karma service. Do you think I understand correctly?

Something like what Blue Ocean provides for Jenkins.

gh-action has planned this feature in Q4 milestones.

[mgol]

As far as I known, we can get BrowserStack's report by karma. So we can parse the report to get the failed browsers and rerun the failed browsers in the karma service.

@ygj6 I have no idea how that would work and, if anything, it would be hacky. We need a native way to re-run a single job and we consider that to be a blocker for adopting any CI system.

[mgol]

Marking as "Request changes" until our concerns with GitHub Actions are resolved.

[mgol]

Closing & re-opening the PR to trigger the EasyCLA check...

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ ygj6 (063d41e, 3fd6dbf)

[mgol]

Two things have happened since my last review:

1. GitHub Actions added support for re-running just the failed workflows.
2. We lost access to Travis 😢
   so I decided to look again at this PR, rebased it & tweaked very slightly and it looks like it works!

Thanks a lot for the PR!

[mgol]

Landed on main in e23190e and on 3.x-stable in b39cfa1.