sonarqube: Update exclusions paths

[kcreddy]

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:

./data_stream/*/lifecycle.yml
./data_stream/*/elasticsearch/ilm/*
./elasticsearch/transform/*
./kibana/tags.yml
./kibana/tag/*
./validation.yml

Related issues

• Relates: [tests] Expand coverage results elastic-package#2704

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

Package google_scc 👍(0) 💚(1) 💔(3)

Expand to view

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

[kcreddy]

CI error (failing system tests inside sentinel_one_cloud_funnel package) is unrelated to this change.

[elasticmachine]

Pinging @elastic/ecosystem (Team:Ecosystem)

[kcreddy]

/test

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: bd667a4

History

• 💔 Build #29820 failed bd667a4

cc @kcreddy

[kcreddy]

@elastic/ecosystem PTAL. This PR prevents skewing of SonarQube coverage quality due to unchecked files by adding exclusions on them. Example: #14809 (comment).

[jsoriano]

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.

[kcreddy]

Closing in favour of adding coverage: elastic/elastic-package#2831