-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run reports automatically & publish them to a repo #2711
Closed
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
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
This is a really nice idea, @yuvipanda! |
3 tasks
I'm not going to be working on this anytime soon, we can pick this back up later if it gets prioritized via our sprint process. |
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
Regularly scheduled 'reports' can help the team keep track of the status of various
parts of our infrastructure. Examples of code written in the recent past that would be
useful as a report include:
and nodes) for Migrate existing GCP GKE based hubs from k8s 1.22+ to 1.24+ #2157 (comment)
different ways images can be specified for the hub (and a bunch of others) for
Identify where 2i2c engineers spend time on image management #2582
The code used for generating these is scattered in gists and slack, and also require
someone with appropriate credentials to run the code, and upload the result somewhere.
There is also no easy way to trace a particular output back to the code that produced it,
nor a way to discover these.
Automated reports
This PR adds a
reports/
directory, which can contain any number of Jupyter Notebooks.Each notebook comprises a 'report', and a GitHub Action will run every week that will:
hide-cell
andhide-input
to control what gets shown in the output.TODO