tractus-x: sonar quality gate configuration and enable Sonar scanning for main branch, other active branches, as well as pull requests - project sldt-digital-twin-registry

Summary

As part of the issue '[Testmanagement] Code Coverage Analysis and Reporting for Digital Twin Registry,' we would like to configure a Sonar quality gate and enable Sonar scanning for the sldt-digital-twin-registry project. This should include the main branch, other active branches, as well as pull requests.

[Testmanagement] Code Coverage Analysis and Reporting for Digital Twin Registry - https://github.com/eclipse-tractusx/sldt-digital-twin-registry/issues/512

project - sldt-digital-twin-registry Github repo - https://github.com/eclipse-tractusx/sldt-digital-twin-registry

Steps to reproduce

sldt-digital-twin-registry sonar - https://sonarcloud.io/project/overview?id=eclipse-tractusx_sldt-digital-twin-registry

What is the current bug behavior?

sonar scanning is only happening to the 'main' branch

What is the expected correct behavior?

we would like to configure a Sonar quality gate and enable Sonar scanning for the sldt-digital-twin-registry project. This should include the main branch, other active branches, as well as pull requests.

Could you please refer the sonar configuration for the project - sldt-bpn-discovery sonar - https://sonarcloud.io/project/overview?id=eclipse-tractusx_sldt-bpn-discovery and configure similar way to sldt-digital-twin-registry project. We assume that it should be possible to configure scanning for the main branch, other GitHub branches, and pull requests without requiring any changes to the existing GitHub Actions configuration in the project. -

sldt-bpn-discovery sonar - https://sonarcloud.io/project/overview?id=eclipse-tractusx_sldt-bpn-discovery sldt-bpn-discovery Github - https://github.com/eclipse-tractusx/sldt-bpn-discovery

Relevant logs and/or screenshots

(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

[Testmanagement] Code Coverage Measurement and Reporting per Tractus-X Project