-
-
Notifications
You must be signed in to change notification settings - Fork 531
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
SonarQube 10.6/Plugin 1.22 Bug: Current edition does not support branch feature #993
Comments
Can you retry this with the snapshot version available for download in the Artifcts section of https://github.com/mc1arke/sonarqube-community-branch-plugin/actions/runs/11872851541 ? This version is the build from #1000 and will prevent Sonarqube starting in the plugin isn't installed properly, which is what I think your issue is. |
So thats why my new Sonarqube stopped starting! haha |
I also encountered the same problem |
@WLY0815 I solved it by adding this to my
and then doing |
Encountered the same issue on Sonarqube 10.5-community, with 1.20.0 plugin version.
The image that is used is 10.5.0-community.
|
Please retry this with 1.23.0 of the plugin since it contains extra safeguards, and raise a new issue if you still have problems |
Describe the bug
I set up the community plugin (v 1.22.0) for my SonarQube server (v10.6.0) and I am running into an error when trying to use the
sonar.branch.name=${BRANCH_NAME}
in my sonar commandline.To Reproduce
Steps to reproduce the behavior:
bitnami-sonarqube-10.6.0-0-r02-linux-debian-12-x86_64-hvm-ebs-nami
extensions/plugins/
directory. I downloaded sonarqube-community-branch-plugin-1.22.0.jarconf/sonar.properties
file with the following contentssudo /opt/bitnami/ctlscript.sh restart
Expected behavior
I expected no errors and that my project would show up in the server
Screenshots
Happy to share more, if needed. The error log says the following
Software Versions
Additional context
This was a brand new EC2 instance that I spun up with hopes of setting up a new SonarQube server. After I ran into that error, I proceeded to try the command line without the
sonar.branch.name=${BRANCH_NAME}
, and (not surprisingly) it works.The text was updated successfully, but these errors were encountered: