-
Notifications
You must be signed in to change notification settings - Fork 109
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
Upgrade Prow autobumper #856
Comments
cc @zuc |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
I think this has been completed, isn't it @cappellinsamuele? |
Yep, I agree! |
/close |
@maxgio92: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Motivation
Open Infra is using the previous version of the Kubernetes Prow autobumper, which is suboptimal based on functionalities and the fact that is not actively maintained.
Feature
We can reference the new Prow Autobumper and using it as artifact - as done here.
Improvement
This way requires in any case to statically declare the periodic Jobs for each repository that contains Prow component configuration (e.g. Peribolos) explicitely, and it's error prone.
It would be good to find a way to autobump Prow components dynamically discovering all the repositories that use them (i.e. now, test-infra and evolution).
Related
See #840
The text was updated successfully, but these errors were encountered: