Existing Apache Sling repositories have been onboarded to https://sonarcloud.io/ as of 16-04-2019 as part of - SLING-8262Getting issue details... STATUS .
Viewing analysis results
All Sling projects are visible at https://sonarcloud.io/organizations/apache/projects?sort=-analysis_date&tags=sling .
The analysis runs for all commits, including pull requests. All pull requests receive a check in addition to the regular Jenkins build, which is afterwards visible in the pull requests check section.
Onboarding new projects
For now, this process is manual and must be done by someone from SonarSource. The recommended way to onboard a project to SonarCloud is to create a SLING Jira issue and ask Fabrice Bellingard (
@bellingard ) to onboard the new repositories. See for instance
SLING-8357Getting issue details...
Administering Sling projects
sling- projects will assigned to the Sling permission template on SonarCloud. If you are part of the Sling group on SonarCloud you will be able to execute various administrative actions. To become part of the Sling group, please raise an issue with INFRA mentioning your GitHub ID after logging in to https://sonarcloud.io/ using your GitHub account at least once.
The administrative tasks to be performed is quite limited, as SonarCloud only knows two dimensions:
- Per organization (is managed by ASF INFRA)
- Per repository (usually not intended as Sling is owning hundreds of repos)
- potentially every Sling SonarCloud Admin can adjust the permissions per repo, but this is not manageable, therefore all changes should rather be done for all projects through the permissions template (require INFRA involvement)
Therefore being in that group is mainly useful for
Note that being part of the Sling Administrators group will not allow you to onboard projects, that is still a manual process.