-
-
Notifications
You must be signed in to change notification settings - Fork 530
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
1.3.0 plugin works with sonar 8.2 ? #112
Comments
@ktibi Build from source from sonarqube8.1 branch and try that version. 8.2 is not supported in 1.3.0 for sure. |
Having had a quick look at the changes in SonarQube 8.2, I think the changes to work with Sonarqube 8.1 should work, with the only real difference being in additional properties being available for configuring the properties for Gitlab decoration which should be backwards compatible. The 1.3.0 release will not work for Sonarqube 8.1 or 8.2 due to the removal of various fields and methods that the currently release version of the plugin needed to use to work with Sonarqube 7.9. I plan on releasing support for SonarQube 8.1 this weekend and will try to get 8.2 sorted at the same time since it looks like less significant changes. |
@mc1arke ok thx ! I can try to test your pre-release if you want on 8.2 ! |
I'm install with no errors.But in got The 404 url is : |
Eagerly waiting for the next release that will hopefully have PR Decoration fully functional for GitHub Enterprise with SonarQube 8.1+.. |
We tried to use the 8.1_sq_branch build against 8.2. The scan's were fine, it create a branch for pullrequest.branch, but it didn't create anything inside PR section in sonarqube as well as no PR decoration on github |
@rverma-jm I have the same issue with gitlab |
have same problem on sonarqube 8.2 ( build 32929 ) with github integration After save configuration, I got next error:
And got error on page GET on page GET |
Hi, I did few changes in the 81 branch and it is working with Sonar 8.2 and Gitlab
Result:
|
I'm not sure, but it works for me;
and for the branch
|
@mc1arke Would it be possible to set up the binding for the pull request decoration when the project is created? At the moment I have to go to every project and set up the Gitlab |
@andrejpetras Thank you! Plugin build from your branch is working with Sonar 8.2 |
Wonderful ! When can we expect a release ? 😄 |
Awesome! Your branch works for me (incl. MR comments in GitLab). Some of your PR parameters are not required for me. But I had to add the parameter
|
EDIT : Sorry I did not see that the code for 8.2 was on the fork, it works fine 👍 |
@bcouetil You need to add the personal key for Sonarqube. The Sonarqube client is using this key to create a comment in the MR |
Works like a charm @andrejpetras. Thank you very much! ❤️ If someone is interested in the compiled version feel free to take the one I just compiled for myself: sonarqube-community-branch-plugin-1.4.0-SNAPSHOT.jar.zip |
I've installed your binaries on my SQ v8.2 (build 32929) This causes an error on my Azure DevOps builds on the code analysis step: ##[error]ERROR: Error during SonarQube Scanner execution Any ideas? |
@parksquare can you provide a more extensive log? Did you put the library in both (all three) places |
It's running with Docker, extensions being a volume pointing to /opt/sonarqube/extensions/plugins in the container. I don't know why it would need to be in any other location? Everything certainly worked before upgrading to SQ 8.2. The logs and UI suggest the plugin is loaded successfully. The problem occurs when the analysis results are POSTed to SQ, which results in a 500. The error is 'Current edition does not support branch feature' I've attached the logs, happy to assist in any way I can |
Being in lib/common is crucial to override the default code saying "Current edition does not support branch feature". You'll see multiple closed issues here on this subject 😉 |
is that a new requirement do you know? |
Sonarqube includes MR analysis in paid version since 8.0, so yes, if you come from 7.X, it's new 😄 |
It was working fine with the community branch plugin and 8.x |
you definitely need to put the new plugin in the 2 (3) locations I pointed out above. Otherwise it won't work. See also the readme installation section here. If you don't have the paths attached you could use |
Has this only become necessary since SQ 8.2? It's not ideal having to mess with files inside the container like that, which is a shame because pointing the plugins and logs locations to volumes was pretty elegant. It kind of defeats the object of running as a container, as it will no longer be possible to destroy it (e.g. on upgrade) without manual intervention again. |
It's now a core fonctionnality that is designed to not be free... I think this is a small price to pay 😅 I'm personnaly using kubernetes, and the official helm chart provides a nice |
This was definitely required in 8.1. We are also running the whole show in
Kubernetes.
…On Sun, Mar 29, 2020 at 11:03 AM Benoît COUETIL ***@***.***> wrote:
It's now a core fonctionnality that is designed to not be free... I think
this is a small price to pay 😅
I'm personnaly using kubernetes, and the official helm chart provides a
nice lib.common option, allowing easy upgrades 😍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#112 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADB4Q56RFCBN7BARILDEQVDRJ5PKTANCNFSM4K47HMFA>
.
|
@mc1arke are you open to a pull request for 8.2 from @andrejpetras? His branch is working for me (using the binaries from @johanneshiry), but the PR decoration images are broken because of some changes here. |
Hi everybody, if anyone else is having issues with proxy when using this plugin: There seems to be a little "flaw" in the code. It uses If anybody needs the patched version: |
Does not seem to work for below configuration. Sonarqube server version: 8.2 Error in ce.log: Also tried removing '/v3' from GitHub URL in ALM Integration section of Sonarqube ( per #100), but that did not help either. |
Hello, im using your plugin @andrejpetras, its works perfect BUT in merge request the images are broken (GitLab): Any ideas about what im doing wrong? Thanks! |
You can set up your own link for the images in general settings: Add this link and try it again: The default configuration is using this link for the images. The |
Hi, is there a way to add only the summary comment and not the sonar issues in Gitlab MR discussion ? |
Hi @andrejpetras |
When will the Pull Request be open? It's very nice to have this plugin for Sonar 8.2 officialy :) |
Hi , you can checkout branches support 8.2, build your own jar and place in dir like instruction. It's worked. I tested many time. |
@dungnt081191 I do not have solution for this issue :( |
Hi bro, one more thing : It's worked with gitlab http server . |
I am running 8.2 and I have tried both the 1.4.0-SNAPSHOT plugins above as well as building a new artifact (1.3.1-SNAPSHOT) from the sq-8_2-support branch. I can see the "Pull Request Decoration" tab under Project Settings but it just says "This feature must first be enabled in the global settings." I have the jar in both I see references to a 3rd directory, Also, like @bcouetil I have installed it through helm, although the plugins.lib section of the helm chart didn't work so I had to copy the jar in the container then restart the server |
The jar has to be generated from @andrejpetras 's fork : https://github.com/andrejpetras/sonarqube-community-branch-plugin/tree/sonarqube82 For the |
@bcouetil thanks for the help, the jar is showing up in lib/common now.
I am using sonarqube-8.2.0.32929 libraries |
The version you downloaded from johanneshiry's comment is actually quite old and doesn't include the fix from issue #100 You should download and checkout the sq-8_2-support branch and compile your own version |
Support for SQ 8.2 - 8.4 released in 1.5.0 of the plugin |
Hello,
We try to deploy the plugin on sonarqube 8.2 but we have a trace :
Our configuration
The text was updated successfully, but these errors were encountered: