infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Klco (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-16985) Question: SonarQube Support for Apache Sling
Date Thu, 06 Sep 2018 15:48:00 GMT
Dan Klco created INFRA-16985:
--------------------------------

             Summary: Question: SonarQube Support for Apache Sling
                 Key: INFRA-16985
                 URL: https://issues.apache.org/jira/browse/INFRA-16985
             Project: Infrastructure
          Issue Type: Improvement
          Components: Analysis
            Reporter: Dan Klco


Infra Team,

The Apache Sling team is exploring options for enabling SonarQube analysis on our codebase
and we wanted to reach out to vet our approach based on the SonarQube documentation:

 * https://wiki.apache.org/general/SonarInstance
 * https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis

Currently, our approach is to update our Jenkins DS Groovy script:
https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup
to add a Sonar publication post-build step.

A couple questions / concerns:

 * Apache Sling has nearly 300 separate projects / Git repos, are there any concerns with
managing this many projects in SonarQube?
 * Are there any concerns with using the publication post step? 
 * What frequency can / should we publish to SonarQube?
 * Is there anything that needs to be setup from the Infra side besides enabling SonarQube
publication in our projects?

Please find below the email thread on the topic:
http://mail-archives.apache.org/mod_mbox/sling-dev/201809.mbox/browser



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message