Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to SonarQube 10.6 #927

Merged
merged 1 commit into from
Aug 11, 2024
Merged

Update to SonarQube 10.6 #927

merged 1 commit into from
Aug 11, 2024

Conversation

phoval
Copy link
Contributor

@phoval phoval commented Jun 26, 2024

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'java.net.FactoryURLClassLoader@6441c486-com.github.mc1arke.sonarqube.plugin.scanner.CommunityProjectBranchesLoader': Resolution of declared constructors on bean Class [com.github.mc1arke.sonarqube.plugin.scanner.CommunityProjectBranchesLoader] from ClassLoader [java.net.FactoryURLClassLoader@6441c486] failed; nested exception is java.lang.NoClassDefFoundError: org/sonar/scanner/bootstrap/ScannerWsClient

@phoval phoval changed the title fix: #926 Update to SonarQube 10.6 #926: Update to SonarQube 10.6 Jun 26, 2024
@phoval phoval changed the title #926: Update to SonarQube 10.6 Update to SonarQube 10.6 Jun 26, 2024
@atalakey4work
Copy link

Dears,

Can someone please merge this PR?

Regards,

@gjabouley-invn
Copy link

gjabouley-invn commented Jul 1, 2024

Hello

please see #904
This is probably not the only change to make 10.6 properly supported, you would at bare minimum need the change in above PR

Also i would recommend against updating the README about the compatibility table, there is already a PR dedicated #906
And in the end this is the responsibility of the maintainer to properly version its plugin.
Probably 1.19 will go for 10.4, 1.20 for 10.5 and 1.21 for 10.6...

@phoval
Copy link
Contributor Author

phoval commented Jul 1, 2024

@gjabouley-invn: #904 do nothing more than upgrade SonarQube version, which is already included in the current PR.
The Readme should be updated in the PR, otherwise it will become outdated, like it is currently.
The Maintainer can force-push the PR to update the versioning.
Jar is available for testing : /~https://github.com/phoval/sonarqube-community-branch-plugin/releases/tag/1.19.1

@gjabouley-invn
Copy link

@mc1arke could you please approve the workflow, so at least we have a build artefact available from the GitHub checks that users can use for deployment?

@gjabouley-invn: #904 do nothing more than upgrade SonarQube version, which is already included in the current PR. The Readme should be updated in the PR, otherwise it will become outdated, like it is currently. The Maintainer can force-push the PR to update the versioning. Jar is available for testing : /~https://github.com/phoval/sonarqube-community-branch-plugin/releases/tag/1.19.1

My point is, as in the linked PR, a 10.5 incompatibility was detected not at init (which makes the issue easy to spot) but rather when configuring a specific feature of the plugin (creating a new DevOps platform integration). This highlight that usages can vary from one setup to another, and even if for your use case the 10.6 works maybe for others with another setup (another ALM, ...) there could still be some other issues to fix.
So it is important for the maintainer to gather user feedbacks for a little while before being confident enough to say "10.6 support is ok".
First thing now it to get the plugin built with GitHub Actions, so people can get a snapshot version from this PR and test it.

About the versioning, well outdated or wrong, both mean incorrect to me 😃

@pedrocarrico
Copy link

pedrocarrico commented Jul 3, 2024

Just installed @phoval 's release and everything seems to be working on 10.6.

@PeteMac88
Copy link

@mc1arke Any update here?

@vamidi
Copy link

vamidi commented Jul 17, 2024

I Also tested @phoval 's release and it looks like it is working on 10.6. No more errors unlike 1.19.0.jar

@bobowang2017
Copy link

@gjabouley-invn: #904 do nothing more than upgrade SonarQube version, which is already included in the current PR. The Readme should be updated in the PR, otherwise it will become outdated, like it is currently. The Maintainer can force-push the PR to update the versioning. Jar is available for testing : /~https://github.com/phoval/sonarqube-community-branch-plugin/releases/tag/1.19.1

/~https://github.com/phoval/sonarqube-community-branch-plugin/releases/tag/1.19.1
this works , good

@this-is-tobi this-is-tobi mentioned this pull request Jul 28, 2024
@anotherandi
Copy link

Hi @mc1arke ,

i tested the "1.19.1" version of phoval in various combinations with SonarQube 10.6.

Tested Sarif import and code coverage.
In SonarQube the analysis of branches and PR worked and showed corerct results.
The PR/MR decoration and summary worked in GitLab and Github.
Tested with sonar-scanner 5.0.1 and 6.1.

Also tested with the current development head of sonarqube (upcoming 10.7)

Could also see the errors mentioned by mohamedazaddou and grandeon after update to 10.6 from 10.4.
But could solve them by deleting /.scannerwork and ~/.sonar.

@mc1arke Could you please approve the proposed changes of this PR and release a 1.20 or 1.21 for SonarQube 10.6?

Thank you for your great work!

@j-martin
Copy link

j-martin commented Aug 8, 2024

I also confirm that this PR is working great on 10.6 (installed with the official Helm chart, if it matters).

@mc1arke mc1arke merged commit 757a33e into mc1arke:master Aug 11, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants