Move build from Travis CI to GitHub Actions?

[iBug]

Recently Travis CI has shown levels of service degradation, including unnecessarily long queue times (> 1 hr) and future plans on more restrictions. On the other hand, GitHub Actions is supported by Microsoft and is believed to be more reliable in terms of usage (free forever for public repositories).

When GHA was originally introduced near the end of last year, it lacked many features so we couldn't switch. Now there is API to trigger workflows manually, it's time that we make this switch.

I have a GHA workflow file for this repo already, and the only thing left to do is to update whatever webhook receiver we have for Smokey and MS wikis to utilize the GH API. An example is provided below which is very easy to understand and port to Ruby.

curl -X POST \
  -d '{"ref": "site"}' \
  -H 'Accept: application/vnd.github.v3+json' \
  -H 'Authorization: token helloworld' \
  https://api.github.com/repos/Charcoal-SE/charcoal-se.github.io/actions/workflows/build.yml/dispatches

Extra: Shall we move the wiki webhook receiver out from MS and put it on AWS Lambda for easier maintenance?

[makyen]

This still isn't complete. Changes to the SD/MS wikis don't trigger a build.

[iBug]

Not sure what was wrong - the URL of GH API is correct, and the webhook endpoint (entrypoint) isn't touched - maybe the token on MS doesn't have admin access to this repo?

cc @Undo1 @ArtOfCode-

[makyen]

Please ignore my last (now deleted) comment. I stupidly was looking at the SD repo's build.yml, rather than the one for this repository.

[makyen]

The config on the GitHub Action side appears to be working. I tried sending a POST using curl similar to what's listed in the first comment in this Issue and the token we use for SD. Doing so did start a build. I also tried a couple of other variations on that POST, which should set the headers a bit closer to what it looks like MS is using. Both of those variations also started a build.

[makyen]

It looks like it's possible to trigger a build in another repository based on a trigger in a different repository.

See:

• Triggering by other repository
• Trigger a GitHub Action when another repository creates a new release, and
• this Google search for "GitHub trigger an action from another repository".

That may make it possible to trigger the site build from wiki changes in the MS and SD repositories without the involvement of MS. I still need to look into this further, so this comment is basically just a placeholder to hold the above links.

[iBug]

Yes it's absolutely possible. We can add an on: gollum Action in MS and SD repositories that calls the workflow_dispatch API. This is essentially moving gollum_hook from MS to GHA.

I previously proposed that we use AWS Lambda for this purpose (I can set it up as soon as I have the necessary access and/or credentials), which is again essentially the same.

[makyen]

If we can do this entirely in GitHub Actions, why introduce yet another dependency by using AWS?

[iBug]

@makyen Quick thoughts: Does @metasmoke have Admin access to this repo? If not, can you add it? I have a feeling this is the point that's blocking our move.