Automate report creation

[bzoz]

Add Github Action that will use node-core-utils and create a reliability report at every UTC midnight.

A sample generated report can be viewed here.

Besides landing, this requires some configuration to the repository itself. Three secret values are needed for the script to run (required by node-core-utils):

• JENKINS_TOKEN - Jenkins access token
• USER_NAME and USER_TOKEN - GitHub user name and access token

I've tried running this with a newly created user, but the ncu-walk failed. It also looks like Jenkins and GitHub tokens must "match". It defiantly works when I gave the script my tokens, we will have to create a robot user and gave it the required access.

[Trott]

@bcoe: Relevant to your interests?

[bcoe]

@bcoe: Relevant to your interests?

@bzoz some context. I've been working with some folks (CC: @cedpeters, @gis727, @madelyndubuk, and @StuartRucker), on building a system that can collect test information over time, identify flaky tests, and open corresponding issues.

@Trott @bzoz, similarly, I was thinking kicking off a nightly node-test-pull-request test run, which pipes to the upstream flaky test tracking service could be a good way to achieve this.

[bzoz]

@bcoe it would be great to have such a system in place.

This reliability repo was a great tool to find those flaky tests. We could have it working again until we get a better solution.

[mmarchini]

I like this, it helps keep a history of failures (especially useful since our jobs are ephemeral), and provides an easy place to search for recurring failures.

[bcoe]

I'm supportive of this as a step in the direction of keeping a closer eye on flaky tests too 👍