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
Proposal: CI Cleanup #15382
Comments
A security problem with centralizing workflows is that it becomes hard to reason about the security properties of permissions needed for each one. However there could be a smaller number of workflows, where they are organized by permissions. Decommissioning and merging is a great idea. I have no opinion on the dashboard. |
I am fully aligned with the proposal, @panyogesh can you please evaluate it as well. If ok, let's have budget for it and let's bring it on TSC for vote. |
+1, Proposal looks fine. |
@tmdzk Are you asking for budget for this, or is it within your current funding? |
It's within current funding |
@tmdzk Can you provide an update on the state of this? Update later: Tim says he is at 25%. |
CI Cleanup
Problem
We are currently using Github Action as our main CI component, GHA UI is definitely not the best and It can be messy, It's very important to have a clean and efficient CI as an open source project, when external contributor open a PR you can see 102 jobs being attached to your pull request. On top of that the Github Action UI can be overwhelming. The proposal is about cleaning all jobs, decommissioning all the unrelevant/unused jobs.
Solution
Multiple things can be done:
Non-goals
None
The text was updated successfully, but these errors were encountered: