-
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
Create a node e2e testjob with Podutils to validate migration #19942
Conversation
/cc @BenTheElder @krzyzacy |
/cc @amwat |
@@ -9,6 +9,10 @@ presubmits: | |||
testgrid-create-test-group: "true" | |||
testgrid-num-failures-to-alert: "10" | |||
always_run: true | |||
decorate: true | |||
extra_refs: |
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.
presubmits don't need the extra_refs for the repo they run on and I think adding it will result in undefined behavior
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.
Great, thanks! Removing!
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.
Removed.
@alvaroaleman if this is right, I can migrate all the jobs from sig-node here to podsubmits (it seems pretty 'trivial', as they use node configs).
Just don't know if there's a way to test like it is in production without actually merging 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.
to my knowledge its not possible to test job changes on prow.k8s.io without actually merging them
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.
(You could copy the job, set optional: true on the copy, create a PR on k/k and check, then remove the copy and update the original here)
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.
Yeah, seems that's the only way: #18338 (comment)
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.
Damn, right then :)
So I can just migrated the required pull-kubernetes-node-e2e
to not have a big change.
I've followed your idea and created a similar job, with other name to test if it works :)
If this is ok we can follow this way and then I can start migrating some other jobs to podutils
503b6ad
to
df1926c
Compare
df1926c
to
313c3ea
Compare
Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]>
313c3ea
to
31e331d
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chaodaiG, rikatz 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 |
@rikatz: Updated the
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. |
Signed-off-by: Ricardo Pchevuzinske Katz [email protected]
This will create a new Node e2e job, using podutil.
The Job is optional, and it was created to validate the migration of the critical job to podutils