Hi,
It seems that there are dedicated Jenkins Jobs responsible for Sonarcloud: https://ci.eclipse.org/sisu/.
For example look at https://ci.eclipse.org/sisu/job/sisu.inject-sonar/configure for details.
Those explicitly configure “sonar.coverage.jacoco.xmlReportPaths” and “sonar.token".
The question is whether we should still rely on Jenkins or fully migrate to GH Actions.
That would require having the “sonar.token” value available as GH organisation/repo secret.
Unfortunately it seems that Jenkins is the only supported build service currently: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/IT_Infrastructure_Doc#builds and https://github.com/eclipse-cbi/jiro/wiki/Jenkins#user-content-How_can_SonarCloud_be_integrated_into_a_Jiro_JIPP
WDYT?
Should I open another ticket to investigate switching to GHA fully? I don’t want to maintain two different build configurations.
Extending https://github.com/eclipse-sisu/sisu-project/blob/main/.github/workflows/build.yml with support for Sonarcloud should be easy to achieve.
Konrad
On 31. May 2024, at 18:33, Tamás Cservenák via sisu-dev <sisu-dev@xxxxxxxxxxx> wrote:
Howdy,
The codebase is ready to be released:
Sonar (we still lack coverage, Jacoco is in place and locally reports are generated but Sonar does not pick it up for some reason):
Please anyone eyeball it, maybe test it, and if anything is missing reply here.
Plan is to release it over the weekend.
Thanks
Tamas
_______________________________________________
sisu-dev mailing list
sisu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sisu-dev
