Skip to content
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

Split Prow config into multiple files #713

Closed
tuminoid opened this issue Apr 26, 2024 · 8 comments · Fixed by #891
Closed

Split Prow config into multiple files #713

tuminoid opened this issue Apr 26, 2024 · 8 comments · Fixed by #891
Assignees
Labels
triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

Prow config is thousands of lines, and hard to manage and read. Split it in the style of https://github.com/kubernetes/test-infra/tree/master/config/jobs

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Apr 26, 2024
@tuminoid
Copy link
Member Author

ping @lentzi90

@lentzi90
Copy link
Member

/triage accepted
Thanks for creating the issue!

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Apr 26, 2024
@Rozzii Rozzii moved this from Backlog to MISC WIP in Metal3 - Roadmap Jun 28, 2024
@metal3-io-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 25, 2024
@NymanRobin
Copy link
Member

/remove-lifecycle stale
Maybe branches that are not maintained anymore could be deleted in conjunction with this as otherwise the configs grow to infinity

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 25, 2024
@tuminoid
Copy link
Member Author

tuminoid commented Aug 5, 2024

/remove-lifecycle stale Maybe branches that are not maintained anymore could be deleted in conjunction with this as otherwise the configs grow to infinity

We do remove branches that are not maintained from the config, but ever since moving from Jenkins jobs to Prow jobs, the config has so many permutations that it is better split for easier maintenance.

@metal3-io-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 3, 2024
@tuminoid
Copy link
Member Author

tuminoid commented Nov 3, 2024

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 3, 2024
@lentzi90
Copy link
Member

lentzi90 commented Nov 4, 2024

/assign

@github-project-automation github-project-automation bot moved this from MISC WIP to Done / Closed in Metal3 - Roadmap Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: Done / Closed
Development

Successfully merging a pull request may close this issue.

4 participants