[
https://issues.apache.org/jira/browse/SLING-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226864#comment-17226864
]
Bertrand Delacretaz edited comment on SLING-9839 at 11/5/20, 5:24 PM:
----------------------------------------------------------------------
Ouch, sorry I missed this, created the duplicate SLING-9880 and adapted
https://github.com/apache/sling-tooling-jenkins/blob/master/vars/slingOsgiBundleBuild.groovy
already - and yes that will probably cause the SonarQube build phase to fail
for modules which do not build with jdk 11.
-Feel free to revert my changes or let me know and I'll cleanup!- I have
reverted my changes to {{vars/slingOsgiBundleBuild.groovy}} as they were likely
to break other things.
was (Author: bdelacretaz):
Ouch, sorry I missed this, created the duplicate SLING-9880 and adapted
https://github.com/apache/sling-tooling-jenkins/blob/master/vars/slingOsgiBundleBuild.groovy
already - and yes that will probably cause the SonarQube build phase to fail
for modules which do not build with jdk 11.
Feel free to revert my changes or let me know and I'll cleanup!
> 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
>
> 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)
