Proposal to transfer jenkins-alerts repo into the Node.js organization #788

We agreed in our Build last meeting #3299 that we start the process to transfer my repository ulisesgascon/jenkins-status-alerts-and-reporting-demo as nodejs/jenkins-alerts. cc: @nodejs/build @nodejs/tsc

This is a experimental Repository that uses Jenkins status alerts and reporting github action to monitor the Node.js Jenkins Machines.

We wanted to receive notifications when Jenkins nodes go down (as shown in this example). In the near future, we plan to implement more advanced features such as alerting us when machines have low disk space levels (as indicated in the report). To ensure that the alerts are working correctly, we intend to create a separate repository before adding numerous notifications to the Build repository.

Full Context

• Motivation details
• How the repo works
• Github Action: Jenkins status alerts and reporting documentation

⚠️ Important:

As you may have noticed, the repository transfer has already been completed. Unfortunately, it was my first time transferring a repository to the Node.js Organization and I did not read the related documentation before beginning the process 🤦. More details

Maintenance:

I will maintain the repository and handle the generated issues.

Roadmap:

The primary objective is to validate this approach and confirm that we can receive notifications when the machines are down. I aim to enhance the Github action to incorporate alerting policies for low available disk space on the machines, enabling us to proactively address the issue before the machines go down due to insufficient space.

Once the tool is established, we may consider archiving the repository and transferring the Github action pipeline to the Build repository.