-
Notifications
You must be signed in to change notification settings - Fork 366
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 kind jobs to the cloud Jenkins #6521
base: main
Are you sure you want to change the base?
Conversation
Can one of the admins verify this patch? |
/test-kind-cloud-networkpolicy |
/test-kind-cloud-conformance |
/test-kind-cloud-ipv6-networkpolicy |
/test-kind-cloud-ipv6-conformance |
/test-kind-cloud-ipv6-only-conformance |
/test-kind-cloud-ipv6-only-networkpolicy |
/test-kind-cloud-ipv6-only-e2e |
/test-kind-cloud-ipv6-networkpolicy |
/test-kind-cloud-ipv6-e2e |
/test-kind-cloud-ipv6-networkpolicy |
/test-kind-cloud-conformance |
44a9629
to
f76915f
Compare
/test-kind-cloud-conformance |
0ce972c
to
aa10062
Compare
/test-kind-all-features-conformance |
/test-kind-whole-conformance |
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.
I'll defer to @XinShuYang on this one but I have 2 questions:
- I see changes related to IPv6 in the PR (
/test-kind-cloud-ipv6-only-networkpolicy
), but the PR title seems to indicate that the changes are for IPv4 only? - do we really have to change the trigger phrase to include "cloud" (e.g.,
test-kind-e2e -> test-kind-cloud-e2e
) or can we keep the same ones? If I understand this PR correctly, "cloud" just means that the tests are being run in the public cloud (GCP)?
You're right, Antonin. The aim of this PR is to migrate all kinds of jobs to the cloud Jenkins according to #6698, not just those for IPv4. @KMAnju-2021 You can include this issue number in the commit message for the future task tracking.
I share the same view. I've discussed this offline with @KMAnju-2021 , and we agree that there is no need to include "cloud" in the kind job name. |
aa10062
to
5813ff8
Compare
/test-kind-e2e |
5813ff8
to
ea51b15
Compare
/test-kind-all |
@KMAnju-2021 It seems |
ea51b15
to
5ecd2cc
Compare
/test-kind-all |
done, thanks! |
#6698 (comment) |
18d34bf
to
13eb730
Compare
Signed-off-by: KMAnju-2021 <km074btcse18@igdtuw.ac.in>
13eb730
to
3491923
Compare
/test-all |
/test-kind-networkpolicy |
/test-kind-conformance |
/test-kind-networkpolicy |
@@ -1206,8 +1206,127 @@ | |||
fingerprint: false |
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.
@KMAnju-2021 Please update the multicluster testbed label in cloud yaml if it has been verified that the multicluster job can pass on the same Kind testbed.
/test-multicluster-e2e |
2 similar comments
/test-multicluster-e2e |
/test-multicluster-e2e |
Signed-off-by: KMAnju-2021 km074btcse18@igdtuw.ac.in
part of: #6698