-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
#782: Add support for Sonarqube 10.1 #786
#782: Add support for Sonarqube 10.1 #786
Conversation
a3228df
to
86df03a
Compare
based on the branch: feature/sonarqube-10_0-support 1. upgrade sonarqubeVersion to '10.0.0.68432' 2. fixed dbClient.componentDao().insert(DbSession session, ComponentDto item, boolean isMainBranch) 3. fixed UT code
86df03a
to
94fdaf0
Compare
Hello, => need to change from: Thanks to that, branch management is back in my SonarQube 10.1 instance. Still need to check if MR are working as expected. |
I'm also facing an issue with building this, are you able to send the built JAR file? |
Get the Artifacts, see as: https://github.com/bluebu/sonarqube-community-branch-plugin/actions/runs/5621946627 |
Sorry for the very late answer. |
Hi all, can anyone here explain why these changes do not merge yet? |
Probably because repo owner has real life. |
Like many others I've been waiting for this to be merged to support SonarQube 10.1. My question is if I were to pull down the artifact from the build of this PR and use it what potential issues would that introduce down the road once an official new version is released? https://github.com/mc1arke/sonarqube-community-branch-plugin/actions/runs/5621946976 |
Yes and no. It's the start of a pattern that often eventually leads to the death of once thriving open-source projects. Been there, done that (on both sides). Once PRs start piling up and go unrecognized by the maintainer(s), the community becomes discouraged and starts loosing interest. The root cause often is the dependency on a single owner/maintainer. If they didn't not recruit other maintainers in time for whatever reason (lack of community interest, own ego, etc.) projects then either die or forks start popping up - and the cycle starts anew. For those generally interested in this topic I recommend "Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure". |
I'll re-create this against master branch once the 10.0 release has been created |
Hello, Thanks for the info above |
Hi again, Regarding the 404 error, this was probably an authentication issue and I managed to workaround it.
When I apply the helm chart with those values I see that in the pod the following variables are set : and also SonarQube is taking those into consideration: However I still don't see the Pull requests option under Administration--> Configuration --> General Settings Am I missing sth? |
hello people, any try this artifact whit the version 10.2.1? |
+1 check issue #782 because current issue is closed. |
based on the branch: feature/sonarqube-10_0-support #754 #753
fixed #782
Get the Artifacts, see as:
https://github.com/bluebu/sonarqube-community-branch-plugin/actions/runs/5621946627