[
https://issues.apache.org/jira/browse/SLING-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239944#comment-17239944
]
Konrad Windszus edited comment on SLING-9839 at 11/28/20, 4:26 PM:
-------------------------------------------------------------------
https://github.com/apache/sling-tooling-jenkins/pull/6 switches only the Sonar
step (i.e. mvn build with Sonar and coverage calculation) to Java 11. In case
that fails the Job is marked as "Unstable" but not failed.
The main build step is unchanged.
was (Author: kwin):
I propose to switch to a parallel build with Java 8 and 11 by default
(https://www.jenkins.io/doc/book/pipeline/syntax/#parallel). Both coverage and
and Sonar should be executed only together with the Java 11 build. That way at
least the Java 8 build will continue to work. We just need to decide whether
the overall build is supposed to be failing in case only Java 11 fails. I would
rather say we should only warn in that case but not fail in case Java 8 is
still successfull. WDYT?
> 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
> Priority: Major
> Time Spent: 20m
> 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)
