Skip to content
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

CAPI: Add operator branch to main jobs #21182

Merged
merged 2 commits into from
Mar 17, 2021

Conversation

alexander-demicev
Copy link
Member

@alexander-demicev alexander-demicev commented Mar 5, 2021

There was created a separate branch for developing new operator. This branch will later be merged in main but now it needs the same CI jobs.

Fixes: kubernetes-sigs/cluster-api#4269

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 5, 2021
@k8s-ci-robot
Copy link
Contributor

Hi @alexander-demichev. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 5, 2021
@k8s-ci-robot k8s-ci-robot added area/config Issues or PRs related to code in /config area/jobs sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Mar 5, 2021
@JoelSpeed
Copy link
Contributor

/ok-to-test
/lgtm

Intention here is to have this as a temporary branch but have all of the existing presubmits running against it to ensure we don't break anything

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 5, 2021
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 5, 2021
Copy link
Member

@fabriziopandini fabriziopandini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 8, 2021
Copy link
Member

@vincepri vincepri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexander-demichev, vincepri

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 8, 2021
@vincepri
Copy link
Member

vincepri commented Mar 8, 2021

@fabriziopandini I don't think we need to hold on that, given that the jobs are going to be the same, but the operator specific ones are additional

Copy link
Member

@fabriziopandini fabriziopandini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fabriziopandini I don't think we need to hold on that, given that the jobs are going to be the same, but the operator specific ones are additional

I think we should sort out the makefile in the operator branch first, because /scripts rely on that (see kubernetes-sigs/cluster-api#4126 (comment))

@@ -9,6 +9,7 @@ presubmits:
branches:
# The script this job runs is not in all branches.
- ^master$
- ^operator-0.4$
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This assumes kubernetes-sigs/cluster-api#4126 (comment) to be addressed first; If we are going to have different makefiles, the /scripts should be updated accordingly

@@ -113,6 +118,7 @@ presubmits:
branches:
# The script this job runs is not in all branches.
- ^master$
- ^operator-0.4$
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it makes sense to run the e2e tests for this branch given that it everything else should not be affected by the operator work?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we might add the operator to e2e or it makes more sense to have a separate job for that?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's for sure, but the question is when
As for now, e2e jobs rely on clusterctl, and according to our latest discussion, the work for getting clusterctl to use the operator will start only when the operator is completed. Does It makes sense to run e2e test on this branch before that moment?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right, let me remove that for now

@@ -143,6 +149,7 @@ presubmits:
branches:
# The script this job runs is not in all branches.
- ^master$
- ^operator-0.4$
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above.

@@ -169,6 +176,7 @@ presubmits:
branches:
# The script this job runs is not in all branches.
- ^master$
- ^operator-0.4$
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above.

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 10, 2021
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 11, 2021
@alexander-demicev
Copy link
Member Author

I added a verify job for the operator since we are using a separate makefile for it

@@ -205,3 +210,25 @@ presubmits:
annotations:
testgrid-dashboards: sig-cluster-lifecycle-cluster-api
testgrid-tab-name: capi-pr-e2e-k8s-latest-main
- name: pull-cluster-api-operator-verify
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not using the same approach we are using for CAPD (calling make targets from a script)

https://github.com/kubernetes-sigs/cluster-api/blob/8bc65c3aa70c416b871b02bfe9cd31e17fd10737/scripts/ci-make.sh#L25?

This avoid to add complexity to test grid and it will make things to nicely fit when we are going to merge back on main

@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 15, 2021
@vincepri
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 16, 2021
@fabriziopandini
Copy link
Member

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 17, 2021
@k8s-ci-robot k8s-ci-robot merged commit aa7a3b0 into kubernetes:master Mar 17, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Mar 17, 2021
@k8s-ci-robot
Copy link
Contributor

@alexander-demichev: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

  • key cluster-api-presubmits-main.yaml using file config/jobs/kubernetes-sigs/cluster-api/cluster-api-presubmits-main.yaml

In response to this:

There was created a separate branch for developing new operator. This branch will later be merged in main but now it needs the same CI jobs.

Fixes: kubernetes-sigs/cluster-api#4269

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/jobs cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable CI jobs for operator branch
5 participants