infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <>
Subject [jira] [Updated] (INFRA-16985) Question: SonarQube Support for Apache Sling
Date Fri, 07 Sep 2018 10:00:05 GMT


Gavin updated INFRA-16985:
    Status: Waiting for user  (was: Waiting for Infra)

I'm assuming you arent going to be publishing all 300+ at the same time?

How often would you feel is useful to your project? 
Would running each of the 300+ staggered over a month be useful enough or do you need more

> Question: SonarQube Support for Apache Sling
> --------------------------------------------
>                 Key: INFRA-16985
>                 URL:
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Analysis
>            Reporter: Dan Klco
>            Assignee: Gavin
>            Priority: Minor
> 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:
>  *
>  *
> Currently, our approach is to update our Jenkins DS Groovy script:
> 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:

This message was sent by Atlassian JIRA

View raw message