-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
tide, Fix require_manually_triggered_jobs tide handling #31687
Conversation
|
Hi @oshoval. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Hi @jmguzik @petr-muller Thanks |
/ok-to-test I think the idea is sound, happy to review when out of WIP and polished |
Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many thanks for handling this edge-case. I added some comments.
Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my POV
/lgtm
/assign @petr-muller
Let's wait on @petr-muller approval.
Thanks
For visibility, there is the function Btw not part of this PR scope, but aint it redundant that |
/retest |
Tide didn't take into account jobs that require manual triggering, on batches and when populating the subpool presubmits. It resulted in missing protection for this kind of jobs. Fix it by acting according the policy, and including require manual triggering jobs in tide decisions. Signed-off-by: Or Shoval <oshoval@redhat.com>
oops commit had the word WIP, removed it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jmguzik, oshoval, petr-muller The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I think the plugin only checks PR title, not commits |
Now that kubernetes/test-infra#31687 is merged, we don't need the workaround anymore. Required manually triggered jobs would be detected as required by tide, and have the same effect as run_before_merge. Signed-off-by: Or Shoval <oshoval@redhat.com>
…in (#3221) * phased plugin: Enable from-branch-protection Signed-off-by: Or Shoval <oshoval@redhat.com> * phased plugin: Remove run_before_merge workaround Now that kubernetes/test-infra#31687 is merged, we don't need the workaround anymore. Required manually triggered jobs would be detected as required by tide, and have the same effect as run_before_merge. Signed-off-by: Or Shoval <oshoval@redhat.com> --------- Signed-off-by: Or Shoval <oshoval@redhat.com>
…in (kubevirt#3221) * phased plugin: Enable from-branch-protection Signed-off-by: Or Shoval <oshoval@redhat.com> * phased plugin: Remove run_before_merge workaround Now that kubernetes/test-infra#31687 is merged, we don't need the workaround anymore. Required manually triggered jobs would be detected as required by tide, and have the same effect as run_before_merge. Signed-off-by: Or Shoval <oshoval@redhat.com> --------- Signed-off-by: Or Shoval <oshoval@redhat.com>
When
require_manually_triggered_jobs
is used, tide doesn't wait for the jobsthat require manual trigger, nor adds them to batches.
This PR fix it, by checking the bp settings, and if the
require_manually_triggered_jobs
feature is enabledfor the branch, then force the jobs that have the following settings:
always_run=false
optional=false
skip_report=false
run_if_changed
andskip_if_only_changed
are emptyor has
run_before_merge=true
(as was already before this PR).Fixes: #31686
Fixes: #31050