-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Feat/4982 unwanted dependency checks #5509
Feat/4982 unwanted dependency checks #5509
Conversation
This PR has multiple commits, and the default merge method is: merge. 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. |
Hi @antoooks. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
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-to-test
@@ -0,0 +1,42 @@ | |||
name: unwanted-dependencies-check | |||
|
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.
can this yaml run on prow job? as we have an issue which want to migrate some actions workflows to prow
#5486
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.
There's a requirement to make the job optional, is it possible in prow to always run it but not cancelling the other pipeline?
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'm not quite sure, but prow can run multiple jobs and choose to make some jobs optional. we might need to investigate prow( but prow is quite a huge project)
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 have confirmed with @natasha41575, it is decided that for this PR we'll still stick to GH action, and if your PR for prow is already merged we can migrate it to prow
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.
my PR for prow is still in pending review, we should merge this first
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.
The changes look good to me. Looks like this test is failing in the CI for this PR. Can it be fixed?
Hi @varshaprasad96, It is expected to be failed on purpose and will be treated as an optional test, so it won't affect approval. (please refer to the referenced issue page) I think since it checks on different parts of kustomize, we should have a separate PR with respective domain owners doing the fix. |
Got it! Thanks! |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: antoooks, varshaprasad96 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 |
Hi! |
Noted, thanks for pointing it out |
@koba1t feedback added |
dd82d0c
to
629f8a9
Compare
d7cc869
to
9f518fe
Compare
remove json file add extra condition to ignore docs changes revert unintended changes revert unintended changes
a95165a
to
35fa808
Compare
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.
/lgtm
/assign @koba1t
FYI, the check meant to be fail because we do have unwanted dependencies :) |
Hi @antoooks For Examplein in CI resultLooks like this dependency were found in the result.
run
|
Hi @koba1t, thank you for checking and finding this, I have found a logic error on Same error also happened on |
New changes are detected. LGTM label has been removed. |
Thanks for your great work, @antoooks! But I'm still concerned that the Because I think this entry for the exception to the unwanted dependencies list. |
Hey @koba1t, thanks for the feedback. Do you mean we need to whitelist dependencies in the PR commit you are referring on your comment? |
with: | ||
title: 🐛 unwanted-dependencies-check failed for ${{ github.sha }} | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
labels: kind/bug |
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 kind/dependencies
is the better label for that issue.
hack/unwanted-dependencies-check.sh
Outdated
READ_PATH=$(realpath ${JSON_PATH_LOCAL}) | ||
else | ||
# Default behavior: pull unwanted-dependencies.json from kubernetes/kubernetes upstream repo | ||
JSON_PATH_URL='https://raw.githubusercontent.com/kubernetes/kubernetes/e51fe4a61cca7f4a0875630da433f280b52c138a/hack/unwanted-dependencies.json' |
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 think that the JSON file may be old.
So, I think maybe better to use the latest file.
I think that is better because we have a few unwanted dependencies that we can't delete. |
hi @koba1t , I have integrated all the changes we discussed. However it seems that the unwanted deps list on k/k has changed. Could you check for deps I need to put into whitelist? |
The above dependencies are listed on the whitelist. Maybe that is better to find the whitelist from the |
Thanks for the note @koba1t , fixed on the subsequent commit |
/close due to deprioritisation |
Addresses #4982
kubernetes/kubernetes
unwanted-dependencies.json
fileunwanted-dependencies-check
Github workflow