-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Migrate all mungers out of mungegithub to prow plugins / periodic jobs #3331
Comments
Is there an issue for migrating approvals into a prow plugin? Has anybody started working on that? I am interested in pursuing it next week. |
I don't think there is an issue specific to that munger yet, just this issue. No one is working on migrating the approval-handler yet, so that would be great! |
discussed during sig-testing today; some mungers can be moved out, some can't (or we'd like to obviate, eg: submit-queue for tide) will update this issue with a full list |
We've got a migration of |
@spiffxp I think we can mark off the release note munger (?) :D |
@BenTheElder Just deployed the changes 😄 I'll mark it. |
#5010 may end up being a suitable replacement for the existing cherry-pick mungers |
Alternatively, it could just continue to create the cherry-pick PR and allow for the current mungers (or their Prow replacements) to layer on top as they had in the past. |
The cherry-pick bot doesn't really replace the cherry-pick mungers because the mungers don't handle the creation of cherry-pick PRs. |
/assign @marun |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/milestone 1.12 |
@nikhita done, and thanks again |
/close |
@spiffxp: 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. |
Umbrella issue.
Most of the mungers can be migrated to Prow plugins and respond to github webhook events but a few need to run periodically without having received an event. These should probably be implemented as kubernetes cron jobs.
EDIT: here's the munger list as of 2018-08-27
approval-handlerbulk-lgtmclose-staleflaky-job-reporterissue-creatorpublisherrelease-note-labelsizetriage-filer[1] - The cherrypick process on github should be rethought and simplified if possible.
[2] - The
comment-deleter
is no longer needed if plugins that create comments remove stale comments at that time.[3] - The
assign-fixes
,inactive-review-handler
,issue-triager
,old-test-getter
,nag-flake-issues
, andstale-pending-ci
are no longer in use so shouldn't be migrated unless they are needed.[4] - The
stale-green-ci
munger could be reimplemented as acommenter
job (eg: periodic-test-infra-retester) but we don't plan on adding this back unless it is sorely missedThe text was updated successfully, but these errors were encountered: