-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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: filter changes using go list output #17397
Conversation
4b85732
to
2b1fab9
Compare
df29299
to
c2b1f95
Compare
a54c37f
to
92c3a7c
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 with some NITs
@urso @jsoriano @andrewkroh |
Agree, changes in other places can also affect deployments in kubernetes. |
* feat: filter changes using go list output * fix: auditbeat trigger
* feat: filter changes using go list output * fix: auditbeat trigger
I see I'm a little late to the discussion, but I wonder how effective this change will be. Can we document what exactly Given that we always add the regular expressions Running the provided script locally I get paths like this:
These are clearly dependencies that should be in Only a small set of packages are prefixed with
No idea why these packages are prefixed with vendor, but the output actually includes these packages twice:
|
It returns the output of
because not all packages have
we can filter them in a follow-up |
* feat: filter changes using go list output * fix: auditbeat trigger
Backport some features added to Jenkinsfile to 7.x branch: * Dry run option. * Docker login. * Git config for generator tests. * Filter changes using go list. These are the cherry-picked changes: * fix: login into the docker registry (#17620) * feat: filter changes using go list output (#17397) * fix: disable workaround on macos (#17750) * ci: set git user configuration if it is not set (#17782) * fix: mount Docker credentials (#17798) * Review dependency patterns collection in Jenkins (#18004) Co-authored-by: Ivan Fernandez Calvo <kuisathaverat@users.noreply.github.com> Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com> Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
What does this PR do?
It extracts the PATH dependencies from the list of Go vendor modules
Why is it important?
This approach is automatic when you add new dependencies, also, it is more accurate filtering better the changes.
Related issues
Relates #16953