Our github action update-urls.yml logs errors if downloads fail (including download veriifications) but continues successfully also on such errors.
We should add a mechanism to count errors in a structured way and then send a notification with an error report. If there is no error also no notification should be send. My suggestion would be to use an email notification. If we use a public distribution list and want to avoid spam, we can configure it as github secret.
To collect the errors, we we should create a structured error state object and count the errors per tool and edition. We should then also count the success so we could e.g. determine and error rate (e.g. gradle 100% error vs. gradle 1% errors). My first draft suggestion:
Our github action update-urls.yml logs errors if downloads fail (including download veriifications) but continues successfully also on such errors. We should add a mechanism to count errors in a structured way and then send a notification with an error report. If there is no error also no notification should be send. My suggestion would be to use an email notification. If we use a public distribution list and want to avoid spam, we can configure it as github secret. To collect the errors, we we should create a structured error state object and count the errors per tool and edition. We should then also count the success so we could e.g. determine and error rate (e.g. gradle 100% error vs. gradle 1% errors). My first draft suggestion:
FYI: I pointed that example also to point out a potential division by zero issue before implementation :)