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.

Sign up for GitHub

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

Jump to bottom

Generate ProwJob YAMLs and automate changes to test jobs #9257

Closed
killianmuldoon opened this issue Aug 21, 2023 · 6 comments · Fixed by #9937
Closed

Generate ProwJob YAMLs and automate changes to test jobs #9257

killianmuldoon opened this issue Aug 21, 2023 · 6 comments · Fixed by #9937
Assignees
@chrischdi
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@killianmuldoon
Copy link
Contributor

killianmuldoon commented Aug 21, 2023 •
edited

CAPI maintains a number of test jobs across 4 branches Kubernetes test/infra for execution in Prow. Currently updating the yamls that define these test jobs is a manual enterprise, even where the same changes need to be made in each and every test job, or with formulaic tasks such as creating jobs for a new release branch.

We should automate editing these yamls so it takes less time to execute and review and gives us more confidence in how we're changing these jobs going forward.

There is prior art for this used by the folks at EKS which could be used as inspiration: https://github.com/aws/eks-distro-prow-jobs/

/assign
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 21, 2023
@killianmuldoon killianmuldoon mentioned this issue Aug 21, 2023
Closed
35 tasks
@killianmuldoon killianmuldoon changed the title Generate our ProwJob YAMLs to automate changes to test jobs Generate ProwJob YAMLs and automate changes to test jobs Aug 21, 2023
@furkatgofurov7
Copy link
Member

Thank you @killianmuldoon!

/triage accepted

Added to the #9104 to track

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 21, 2023
@furkatgofurov7
Copy link
Member

Based on the agreement during the call triaging #9104, setting the priority to:

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 21, 2023
@furkatgofurov7
Copy link
Member

furkatgofurov7 commented Oct 18, 2023 •
edited

@killianmuldoon 👋🏼 Just wanted to check in and know if there is any update on this issue or if Release Team members can help to move this forward. Thanks.

@killianmuldoon
Copy link
Contributor Author

If someone has time to pick this up please do - I'm happy to pair on it and help if folks want.

@killianmuldoon
Copy link
Contributor Author

/unassign

@chrischdi
Copy link
Member

/assign

@chrischdi chrischdi mentioned this issue Dec 29, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chrischdi chrischdi

Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
CAPI v1.7 release improvement tasks
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

🌱 hack: implement generator for prowjobs chrischdi/cluster-api
4 participants
@chrischdi @k8s-ci-robot @furkatgofurov7 @killianmuldoon