sonar exclusion for acs commons

[PradeepMC1]

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.

<properties>

        ....

        ...

        <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]

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-conf...

[Uppari_Ramesh]

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.

[PradeepMC1]

Hi @Uppari_Ramesh  @SantoshSai ,

So, there is no way to override the cloud pipeline's sonar exclusion ?

[Uppari_Ramesh]

@PradeepMC1 Please check this once with Adobe CSE if there is any way.

Thanks 

Ramesh