Relay Jenkins events to Github Action workflows

[phillipj]

These changes are meant to allow us to write GitHub Actions in selected repositories in the nodejs github organization, as a reaction to Jenkins events.

It works by dispatching repository events, which we can use as triggers for GitHub Action workflows.

Here's a concrete repository dispatch event caused by the Jenkins job node-test-commit-osx:

event_type: jenkins.node-test-commit-osx.start or jenkins.node-test-commit-osx.end

client_payload:
{
  "identifier": "node-test-commit-osx",
  "status": "success",
  "message": "tests passed",
  "commit": "8a5fec2a6bade91e544a30314d7cf21f8a200de1",
  "url": "https://ci.nodejs.org/job/node-test-commit/3157/",
  "ref": "refs/pull/12345/head"
}

Refs:

• Modernizing the project #264
• GitHub Action docs: repository_dispatch
• GitHub REST API docs: Create a repository dispatch event

[phillipj]

Thanks for having a look @mmarchini! Since you know the practical use cases better than me, I'd love your feedback on the following ramblings...

On second thought, I've got some doubts with regards to the event type names suggested with these changes. Especially having the job names, like node-test-commit-osx, as part of event type names in mind 🤔

Trying to put myself in the using end of these dispatched events, I get concerned they'll end up being awkward to consume:

on:
  repository_dispatch:
    types: [ jenkins.node-test-commit-osx.start, jenkins.node-test-linter.start, jenkins.node-test-pull-request.start ] # ..and the list goes on

Would it make sense to use jenkins.job.start | jenkins.job.end instead:

on:
  repository_dispatch:
    types: [ jenkins.job.start ]

and then filter on github.event.client_payload.identifier when needed?

[mmarchini]

Oh, I didn't include one of my ideas in the PR. We could have wildcards: jenkins.node-test-commit-osx.start, jenkins.*.start, jenkins.node-test-commit-osx.*, jenkins.*.*. But that leads to quad-dispatching. Personally, I think folks will be interested in one Job instead of many. We can change that in the future if folks come up with use cases where multiple jobs are needed.

[phillipj]

Ahhh alrighty then, let's go with this as is.

[phillipj]

It's alive.

{
  "name": "bot",
  "hostname": "infra-rackspace-debian8-x64-1",
  "pid": 27894,
  "req_id": "a66d6390-38cd-11eb-a22b-f5ad452d226c",
  "identifier": "node-test-commit-aix",
  "event": "end",
  "level": 20,
  "msg": "Relaying jenkins.node-test-commit-aix.end to nodejs/node",
  "time": "2020-12-07T20:49:07.658Z",
  "v": 0
}