-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
fix(inputs.jenkins): Filter after searching sub-folders #14105
Conversation
Currently, the Jenkins plugin will apply the user filter to directory names immediately. If the directory does not match the filter it would toss the folder. This prevents traversing into the folder itself where a user might want a job inside the folder. This change will move the filtering operation to occur after we kick off directory traversal. The changes to the tests were necessary since we never went into the folders correctly. The test results are the same, the changes are to the response our mock jenkins server provides. fixes: influxdata#14054
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
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 for the fix @powersj!
(cherry picked from commit 3fbe624)
Currently, the Jenkins plugin will apply the user filter to directory
names immediately. If the directory does not match the filter it would
toss the folder. This prevents traversing into the folder itself where a
user might want a job inside the folder.
This change will move the filtering operation to occur after we kick off
directory traversal. The changes to the tests were necessary since we
never went into the folders correctly. The test results are the same,
the changes are to the response our mock jenkins server provides.
fixes: #14054