[
https://issues.apache.org/jira/browse/OAK-11271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated OAK-11271:
----------------------------------
Description:
Currently SonarCloud analysis is disabled in
https://github.com/apache/jackrabbit-oak/commit/6b3512f120d061e523059797f04b26eb6f0c43ab
with GHA.
As [automated
analysis|https://docs.sonarsource.com/sonarcloud/advanced-setup/automatic-analysis/]
lacks some functionality (code coverage) we should explicitly trigger it from
GitHub actions as outlined in
https://docs.sonarsource.com/sonarcloud/advanced-setup/ci-based-analysis/sonarscanner-for-maven/.
However SonarQube now requires Java17 and we only build with Java 11. Maybe one
can leverage
https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/analysis-parameters/#jre-autoprovisioning
or use an approach like in
https://github.com/apache/jackrabbit-filevault-jenkins-lib/blob/942dfe629c3cb3eb0aa1ae2b504393f2f927d26f/vars/vaultStageBuild.groovy#L70
which executes SonarCloud with a dedicated JRE separately after the main build.
was:
Currently SonarCloud analysis is disabled in
https://github.com/apache/jackrabbit-oak/commit/6b3512f120d061e523059797f04b26eb6f0c43ab
with GHA.
As [automated
analysis|https://docs.sonarsource.com/sonarcloud/advanced-setup/automatic-analysis/]
lacks some functionality (code coverage) we should explicitly trigger it from
GitHub actions as outlined in
https://docs.sonarsource.com/sonarcloud/advanced-setup/ci-based-analysis/sonarscanner-for-maven/.
> Reenable SonarCloud with GHA
> ----------------------------
>
> Key: OAK-11271
> URL: https://issues.apache.org/jira/browse/OAK-11271
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: continuous integration
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> Currently SonarCloud analysis is disabled in
> https://github.com/apache/jackrabbit-oak/commit/6b3512f120d061e523059797f04b26eb6f0c43ab
> with GHA.
> As [automated
> analysis|https://docs.sonarsource.com/sonarcloud/advanced-setup/automatic-analysis/]
> lacks some functionality (code coverage) we should explicitly trigger it
> from GitHub actions as outlined in
> https://docs.sonarsource.com/sonarcloud/advanced-setup/ci-based-analysis/sonarscanner-for-maven/.
> However SonarQube now requires Java17 and we only build with Java 11. Maybe
> one can leverage
> https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/analysis-parameters/#jre-autoprovisioning
> or use an approach like in
> https://github.com/apache/jackrabbit-filevault-jenkins-lib/blob/942dfe629c3cb3eb0aa1ae2b504393f2f927d26f/vars/vaultStageBuild.groovy#L70
> which executes SonarCloud with a dedicated JRE separately after the main
> build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
