-
Notifications
You must be signed in to change notification settings - Fork 489
sonarqube: Update exclusions paths #14880
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
Conversation
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
asset |
1976.28 | 1449.28 | -527 (-26.67%) | 💔 |
audit |
3144.65 | 2645.5 | -499.15 (-15.87%) | 💔 |
source |
66666.67 | 35714.29 | -30952.38 (-46.43%) | 💔 |
To see the full report comment with /test benchmark fullreport
CI error (failing system tests inside |
Pinging @elastic/ecosystem (Team:Ecosystem) |
/test |
|
💚 Build Succeeded
History
cc @kcreddy |
@elastic/ecosystem PTAL. This PR prevents skewing of SonarQube coverage quality due to unchecked files by adding exclusions on them. Example: #14809 (comment). |
I would prefer to update coverage reports in elastic-package, at least for the files covered by some test. Doing this in elastic/elastic-package#2831. |
Closing in favour of adding coverage: elastic/elastic-package#2831 |
Proposed commit message
Currently almost all PRs that has changes to transform fail
SonarQube checks because transform code is not covered
by any of the tests. Example: #14629 (comment)
Until elastic/elastic-package#2704 is implemented, this
temporary fix ensures SonarQube skips following files where
the coverage is not yet offered by
elastic-package
tests,thus avoiding false positives:
Related issues