Sonar configuration on Cloud Manager pipeline

[BrunoMM]

Hi everybody.

I am trying to add a folder with frontend files to sonar analysis scope. However, using properties on pom.xml doesn't make any difference:

<properties>
   <sonar.sources>src/main</sonar.sources>
</properties>​

I added this to my pom.xml, but i found in my logs something about properties being removed because a conflict.

[main] [INFO] Scanning projects to remove conflicting properties...
.
.
[main] [INFO] Removing property keys [sonar.sources].​

This does not happen in my local environment, just in the cloud manager pipelines. I use the same maven version (3.6.0) that i found in the pipelines's logs.

Now, i am trying to understand why it is removing my config? And if there is a way to get around this? I have tried some different ways of configuration, but with no success. Any help will be appreciated.

Thanks in advance.

[aanchal-sikka · Accepted solution]

Hello @BrunoMM 

The Cloud manager acts on Adobe recommended project structures. It has some default settings which are used in all projects.

If you want to append/configure any behaviour in a certain way (example: scope of sonar analysis, code coverage %), then please raise a support ticket. They might be able to assist you or they will share feedback acoordingly

[BrunoMM]

First of all, thank you very much for your answer.

We raised a ticket, but unfortunately it was not possible to achieve what we intended to do. They suggested to use a third party tool for it.

Thanks again for the help.

[aanchal-sikka]

Thanks for sharing the info with us @BrunoMM 

Have a wonderful day !

[TarunKumar]

Hi @BrunoMM ,
Can you try using plugin "jacoco-maven-plugin" in the pom file and check for the sonar coverage.

Thanks
tarun

[kautuk_sahni]

@BrunoMM Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.