You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/12/04 18:38:00 UTC

[jira] [Commented] (SLING-9839) Jenkins: Sonarcloud analysis with Java 11

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

Konrad Windszus commented on SLING-9839:
----------------------------------------

Fixed in https://github.com/apache/sling-tooling-jenkins/commit/0ae97fc92104c131bc42b1a6993316652447e004.

> Jenkins: Sonarcloud analysis with Java 11
> -----------------------------------------
>
>                 Key: SLING-9839
>                 URL: https://issues.apache.org/jira/browse/SLING-9839
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> As SonarSource is stopping support for Java 8 analysis (https://sonarcloud.io/documentation/appendices/move-analysis-java-11/), we should switch to matrix builds with Jenkins with Java 8 and 11 builds in parallel (https://www.jenkins.io/blog/2019/12/02/matrix-building-with-scripted-pipeline/ ).
> The Java 8 build should be deployed to Apache Snapshots (for backwards compatibility reasons). The Java 11 build should be used for coverage analysis and sonar execution..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)