Hi devs,
Right now we have a single org on SonarQube Cloud which lists both repos from the xwiki and xwiki-contrib GitHub orgs.
However, I’ve noticed that there’s now a binding to the GitHub org. For example:
This allow to bind individual SonarQube projects to their repos, allowing to decorate PRs (and probably more).
The problem is that we cannot enable PR decoration for contrib projects since they’re located in the wrong GH org on sonarcloud.
So it seems that SonarCloud is pushing us to have 2 organizations (one per GH org) and this proposal is about doing this.
Technically, I think it means:
- Create a new “XWiki Contrib” org in SonarCloud
- Configure our build for contrib projects to point to the right sonarcloud org. Right now the org is defined at xwiki-commons/pom.xml at 758bffe15a9bf83e15cedb95b6beea10155e1baa · xwiki/xwiki-commons · GitHub. We probably need to:
- Redefine
<sonar.organization>xwiki-contrib</sonar.organization>in the contrib parent at parent/parent-commons/pom.xml at master · xwiki-contrib/parent · GitHub - Also allow passing a jenkins pipeline property to set the sonar org, in our JenkinsFile files (for contrib projects that cannot upgrade their parent poms). And use that property at xwiki-jenkins-pipeline/vars/xwikiBuild.groovy at 70c77783374ba6940b3b4416101c384512d21413 · xwiki/xwiki-jenkins-pipeline · GitHub
- Redefine
WDYT?
Thx
