[POC] Script to monitor all ETS package cron job #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background: Currently, inspection of the cron jobs requires someone to go to Travis.com, type in the name of the ETS package they want to check, look for the build that has the cron-job symbol on, and then loop over the ETS packages we have. This gets more and more laborious as the number of repositories grow.
It is possible to run a script to gather and present the status of the CI cron jobs for all the ETS packages, in one place.
This PR provides a proof-of-concept for future consideration. It provides a script that obtains the cron job results on GitHub Actions using its web API (Travis provides a web API so we can do the same thing), and then writes a file presenting the report.
To run, follow the instruction in
check-cron/README.rst. Thecheck-cron/result.mdfile is the file written by the script.It should be relatively easy to create a GitHub Actions workflow just to run the script and update the file on the repo. Then we can access the result with a single URL.
This PR is open for the purpose of demonstrating an idea and persisting work towards it. It can be closed without merging.
(Note: It is not necessary for this script to be on master in order to run it on GitHub Actions.)