antrea Migrate kind jobs to the cloud Jenkins

Signed-off-by: KMAnju-2021 [email protected] part of: #6698

Jul 09 '24 10:07 KMAnju-2021

Can one of the admins verify this patch?

Sep 29 '24 10:09 antrea-bot

/test-kind-cloud-ipv6-conformance

Sep 29 '24 16:09 KMAnju-2021

/test-kind-cloud-ipv6-only-conformance

Sep 29 '24 17:09 KMAnju-2021

/test-kind-cloud-ipv6-only-networkpolicy

Sep 29 '24 19:09 KMAnju-2021

/test-kind-cloud-ipv6-networkpolicy

Sep 30 '24 12:09 KMAnju-2021

/test-kind-cloud-conformance

Oct 01 '24 05:10 KMAnju-2021

/test-kind-cloud-conformance /test-kind-cloud-e2e

Oct 01 '24 06:10 KMAnju-2021

/test-kind-all-features-conformance

Oct 01 '24 10:10 KMAnju-2021

/test-kind-whole-conformance

Oct 01 '24 10:10 KMAnju-2021

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?

You're right, Antonin. The aim of this PR is to migrate all kinds of jobs to the cloud Jenkins according to https://github.com/antrea-io/antrea/issues/6698, not just those for IPv4. @KMAnju-2021 You can include this issue number in the commit message for the future task tracking.

* 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)?

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.

Oct 02 '24 02:10 XinShuYang

/test-kind-e2e

Oct 03 '24 06:10 KMAnju-2021

/test-kind-all

Oct 03 '24 11:10 XinShuYang

@KMAnju-2021 It seems all-feature-conformance and whole-conformance can not be triggered by "test-kind-all", did you update them in Jenkins? Also, if all kind jobs have been migrated to the new Jenkins instance, please disable all related jobs in the source instance to prevent the old jobs from being triggered.

Oct 03 '24 11:10 XinShuYang

/test-kind-all

Oct 03 '24 11:10 KMAnju-2021

@KMAnju-2021 It seems all-feature-conformance and whole-conformance can not be triggered by "test-kind-all", did you update them in Jenkins? Also, if all kind jobs have been migrated to the new Jenkins instance, please disable all related jobs in the source instance to prevent the old jobs from being triggered.

done, thanks!

Oct 03 '24 11:10 KMAnju-2021

https://github.com/antrea-io/antrea/issues/6698#issue-2552642146 Need to support ipam trigger phrase for kind in gcp cloud in a separate PR

Oct 04 '24 06:10 rajnkamr

/test-kind-ipv6-all

Oct 17 '24 04:10 XinShuYang

/test-kind-ipv6-all

Oct 18 '24 06:10 KMAnju-2021

/test-kind-ipv6-networkpolicy

Oct 18 '24 09:10 KMAnju-2021

/test-all

Oct 21 '24 06:10 rajnkamr

/test-kind-ipv6-all

Oct 23 '24 06:10 KMAnju-2021

/test-kind-whole-conformance /test-kind-all-features-conformance

Nov 04 '24 04:11 KMAnju-2021

/test-all-features-conformance /test-whole-conformance

Nov 07 '24 06:11 XinShuYang

/test-all-features-conformance

Nov 07 '24 07:11 KMAnju-2021

/test-whole-conformance

Nov 07 '24 07:11 KMAnju-2021

LGTM Maybe at some point we can stop documenting the /test-kind-* commands, if the corresponding /test-* command does the same thing (e.g., /test-kind-whole-conformance and /test-whole-conformance seem to be aliases).

Yes, in the second stage of job migration, we plan to remove redundant jobs, will include this enhancement in the next release with job yaml update. cc @KMAnju-2021

Nov 08 '24 02:11 XinShuYang

antrea antrea copied to clipboard

Migrate kind jobs to the cloud Jenkins

antrea
antrea copied to clipboard