[
https://issues.apache.org/jira/browse/SLING-8262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758292#comment-16758292
]
Robert Munteanu edited comment on SLING-8262 at 2/1/19 3:19 PM:
----------------------------------------------------------------
*Current status*:
* enable SQ analysis for all {{master}} branch builds (/)
* create shared filter in SonarQube at
https://builds.apache.org/analysis/dashboard/index?did=5 (/)
* enable SonarQube analysis on pull requests (x) - see
https://lists.apache.org/thread.html/46ed5b81cb17303387442144d44eb3080b8e0c45c28eee99ca4520d8@%3Cbuilds.apache.org%3E
* configure Sling-specific quality gate that applies to all Sling projects (?)
* configure Sling-specific quality profile that applies to all Sling projects
(?)
was (Author: rombert):
* enabled SQ analysis for all {{master}} branch builds
* created shared filter in SonarQube at
https://builds.apache.org/analysis/dashboard/index?did=5
> Add SonarQube analysis to Jenkins jobs
> --------------------------------------
>
> Key: SLING-8262
> URL: https://issues.apache.org/jira/browse/SLING-8262
> Project: Sling
> Issue Type: Improvement
> Components: Build and Source Control
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the pipeline jobs it becomes simple to run a SonarQube analysis ( see
> https://cwiki.apache.org/confluence/display/INFRA/Multibranch+Pipeline+recipies
> ) so let's do that.
> We should also look if this can be done for pull requests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
