-
Notifications
You must be signed in to change notification settings - Fork 84
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
upgrade depguard to v2 #844
Conversation
/hold wait istio/tools#2490 |
desc: "operator should not be imported" | ||
- pkg: istio.io/istio/istioctl | ||
desc: "istioctl should not be imported" | ||
# configuration for depguard | ||
packages-with-error-message: |
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.
delete these lines after build-image upgraded
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.
thanks. I think this is close to what I test in the other repos. I'll give it a another try in them in the morning and if things work, I think we can try merging this.
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.
maybe we should add test for this,
checkout code from other repo then run make lint
?
Signed-off-by: hejianpeng <[email protected]>
I believe the processing here is a little bit circular, and that's what we need to take into consideration. When a common-files PR merges, there are a number of post-submit jobs. One set is related to calling make update-common in the various repos updating their common-files to match the submitted PR. Another job updates the test-infra file job definitions to use the new image in the pipeline. Normally, we let the first set of jobs update the common-files to make sure everything seems OK, then we update the pipeline to use the new image. Note that the first set of PRs across the repos still use the image called out in the pipeline, and I think this is one of the cases, we need to be a little different. Since the repo PRs will have the new .golangci.yml but using the existing pipeline image, those PRs will fail the lint-go. We can work around that by merging the image updating PR in test-infra right away. This should cause the pipeline jobs to use the new image and we will have the new .golangci.yml in common. The question is if what we have here will work across all the repos. |
Comments (with editing as the repos are tested) Running test-infra: OK
ztunnel: OK |
@howardjohn Any last minute thoughts on merging this and merging the test-infra right away so the lint test passes in the repos. |
TBH I don't really get the problem, lets just merge something :-) |
OK. Removing DNM. |
related to istio/tools#2490