You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Pierre Smits (JIRA)" <ji...@apache.org> on 2019/05/26 10:00:00 UTC

[jira] [Comment Edited] (OFBIZ-7963) Create a Gradle Sonar task

    [ https://issues.apache.org/jira/browse/OFBIZ-7963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848385#comment-16848385 ] 

Pierre Smits edited comment on OFBIZ-7963 at 5/26/19 9:59 AM:
--------------------------------------------------------------

Jacques,

To clarify some things:
# The Jenkins+Sonar aspect is based on a sonarqube service provided by the ASF that has been deprecated in favour of the 3rd party Sonar service (sonarcloud.io). So there is only the in-house CI services (buildbot and Jenkins). I have explained in the referenced tickets that the in-house Sonar service was going away. 
I have also explained that in order to have this (code analysis) working, the patch is required. So without the patch there is no code analysis. 
# CI is not vague! Whether projects want to use CI (or not, and with what) is up to the projects. The ASF provides only buildbot and Jenkins. Travis is not an ASF service. It is a 3rd party service.
# Ultimately it is you who is concerned about buildbot+sonar. The rest does not care, as long as the service to the project is as expected.
# Everyone with privileges has access to ASF services, or can request them via INFRA.


was (Author: pfm.smits):
Jacques,

To clarify some things:
# The Jenkins+Sonar aspect is based on a sonarqube service provided by the ASF that has been deprecated in favour of the 3rd party Sonar service (sonarcloud.io). So there is only the in-house CI services (buildbot and Jenkins). I have explained in the referenced tickets that the in-house Sonar service was going away. 
I have also explained that in order to have this (code analysis) working, the patch is required. So without the patch there is no code analysis. 
# CI is not vague! What projects use to have CI (or not, and with what) is up to the projects. The ASF provides only buildbot and Jenkins. Travis is not an ASF service. It is a 3rd party service.
# Ultimately it is you who is concerned about buildbot+sonar. The rest does not care, as long as the service to the project is as expected.
# Everyone with privileges has access to ASF services, or can request them via INFRA.

> Create a Gradle Sonar task
> --------------------------
>
>                 Key: OFBIZ-7963
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7963
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Assignee: Pierre Smits
>            Priority: Minor
>         Attachments: OFBIZ-7963-sonar.patch, OFBIZ-7963-sonar.patch, OFBIZ-7963-sonar.patch
>
>
> As ever the devil is in details. There is no longer a Sonar plugin available https://docs.gradle.org/current/userguide/sonar_plugin.htmland we should rather refer to http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Gradle
> Anyway the most important part is to revivify INFRA-3590



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