sonar exclusion for acs commons

Question

Hello there,

I am trying to avoid sonar scan for third party packages/code for some reasons in cloud manager CI/CD pipeline.

Tried configuring below configuration in root pom file.

....

...

<sonar.exclusions>

**/apps/acs-commons/**,

**/apps/acs-commons*/**,

**/ui.apps/src/main/content/jcr_root/apps/acs-commons/**,

**/ui.content/src/main/content/jcr_root/apps/acs-commons/**,

**/core/src/main/java/com/adobe/acs/**,

**/etc/acs-commons/**

</sonar.exclusions>

</properties>

But this dint help me. Any thoughts ?. is it possible to override the pipeline so that our configuration gets priority for scanning ? or its not possible at all to avoid this scanning ?

SantoshSai · Accepted Answer

Hi @pradeepmc1,I think, Adobe does not use your project’s sonar.exclusions configuration by default.As I know, The code quality scan in Cloud Manager is centrally controlled by Adobe and runs its own set of rules with SonarQube.This means that your <sonar.exclusions> or even a custom sonar-project.properties is ignored in the Cloud Manager pipeline.Please refer if this helps: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sonar-s-code-scanning-configuration/m-p/613769

Uppari_Ramesh · Answer

Hi @pradeepmc1 , I had this issue earlier and as @santoshsai mentioned it will not work for cloud manager pipeline. But it works for your own CI CD pipeline like Azure pipelines. Thanks,Ramesh.

Sign up

Login with SSO

Login to the community

Login with SSO