[
https://issues.apache.org/jira/browse/JENA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825205#comment-16825205
]
Aaron Coburn commented on JENA-1704:
------------------------------------
What I've done with some of my own projects is to add the sonar analysis to an
\{after_success} section in the travis configuration. That way, it can't ever
fail a build; sometimes sonarcloud might be down, etc. I have also found that
it is best to run the \{sonar:sonar} analysis only for one particular
environment – for example, run the analysis on openjdk8 but not on oraclejdk8
(it doesn't matter so much which one, just pick one environment).
> Enable Apache Sonar reports
> ---------------------------
>
> Key: JENA-1704
> URL: https://issues.apache.org/jira/browse/JENA-1704
> Project: Apache Jena
> Issue Type: Improvement
> Components: Build
> Reporter: A. Soroka
> Assignee: A. Soroka
> Priority: Trivial
>
> Apache offers a Sonar service at [https://builds.apache.org/analysis.] We
> should take advantage of it in a non-intrusive way. Enabling Sonar analysis
> must not annoy anyone working on the codebase or make development less
> pleasant, so it must be done carefully.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
