-
Notifications
You must be signed in to change notification settings - Fork 74
changed reconciler, UT and e2e to be v1beta1 #1264
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: capri-xiyue 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 know is WIP, but do you think is possible to separate the CloudBuildSource move to v1beta1 in another PR? As that one is not high priority, and I think we don't have E2E tests for it yet? |
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.
It looks like this PR is doing multiple things. I recommend breaking it up:
- Create CloudBuildSource v1beta1 version.
- v1beta1 - Sources #812 and Sources v1beta1 conversions #827 are how it was done for other sources.
- Switch reconcilers to use the v1beta1 versions.
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-google-knative-gcp-integration-tests:
|
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-google-knative-gcp-wi-tests:
|
I didn't realize I need to create CloudBuildSource v1beta1 version until I ran into build failure. I will try to see whether it's easy to break it into two PRs |
/retest |
/test pull-google-knative-gcp-build-tests |
/test pull-google-knative-gcp-unit-tests |
1 similar comment
/test pull-google-knative-gcp-unit-tests |
All E2E tests related to pubsub channel broke again. |
Can you update the description and release notes of the PR? We auto-generate the release notes based on that, so it's better to include this... I'm willing to let this in because we are kind of in a hurry and there are other P1s. I don't see a problem as we are not releasing CloudBuildSource for now. If @Harwayne agrees, I think after the comments are resolved, we can get this in asap... |
- name: v1alpha1 | ||
served: true | ||
storage: true | ||
- name: v1beta1 | ||
served: true | ||
storage: 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.
@Harwayne shall we change everywhere to?
versions:
- name: v1alpha1
served: false
storage: false - name: v1beta1
served: true
storage: true
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 don't think I can change it to things as above.
Otherwise, we can't create v1alpha1 resources anymore
It looks like it should be
versions:
- name: v1alpha1
served: true
storage: false - name: v1beta1
served: true
storage: true
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.
ok, please sync with Adam tomorrow, as he knows better about this... If it passes, I think we can let it in...
/retest |
The following is the coverage report on the affected files.
|
Thanks @capri-xiyue this huuuugeee change!!! /lgtm |
Fixes #1168
Fixes #1211
Proposed Changes
Release Note
Docs