I am currently on SonarQube Community Edition and I am trying to Integrate SonarQube with BitBucket. I have created an OAuth Consumer in my BitBucket Account and when I try to add it in SonarQube's BitBucket Cloud I am getting an error which is not properly complete I Guess (Unknown url : /api/alm_settings/create_bitbu... )
I don't know what I am doing wrong or if SonarQube Community Edition doesn't allow me to integrate BitBucket ALM. I am attaching a screenshot of the same
Cheers,
As it turns out, I have solved this issue and am posting the solution for whoever needs it.
It just so happens that this was an issue with the version of SonarQube I had. I updated SonarQube to the latest version(v9.6.1) and that resolved my issue.
Cheers,
Related
I have a PR analysis done on a project in Azure pipeline and the analysis doesnt show up any issues in sonarUI for the code.
But when the PR is merged in to the branch and analysis is performed then the issues are generated for the same piece of code.
using SonarQube 8.5
Could someone explain the reason??
What type of Azure DevOps are you using? The cloud offering, Azure DevOps Services (VSTS)? Or the on-premises offering, Azure DevOps Server (TFS)?
According to the introduction from the docs about Pull Request Analysis in SonarQube, it seems that Azure DevOps Services is not supported for Pull Request Analysis in SonarQube.
If you are using Azure DevOps Services, you can try the method below to see if it can work:
Install a Self-hosted agent on the machine your SonarQube server is hosting. And use this agent to run your pipeline. Before analyzing your Pull Requests, make sure the Pull Request branch is checked out.
[UPDATE]
According to your comments,
I have a PR analysis done on a project in Azure pipeline and the analysis doesnt show up any issues in sonarUI for the code. But when the PR is merged in to the branch and analysis is performed then the issues are generated for the same piece of code.
The PR build and the CI build have the same configuration, and the only difference is the trigger type. Due to the CI build can work as expected, the configuration you set in the Azure pipeline should be correct.
I see this happenning intermittently...previously with 8.0 version this issue never happened..after the upgradation to 8.5..I can see this issue happening
You can try the build pipeline with version 8.0 to see if it still works as expected. And compare the output logs in the build pipeline between version 8.0 and 8.5.
If it works fine on version 8.0, it means the Azure pipeline can work normally, and the issue should occur on the version 8.5 itself. If so, I recommend that you can open a topic on the SonarSource Community to get more help.
I want to use SonarQube for PL/SQL. I downloaded the plugin from the SonarQube Site and placed it into $SONARQUBE_HOME/extensions/plugins. Then I restarted the SonarQube Server but it didn't start up. When I removed the plugin it was working.
How can I resolve this issue?
The PL/SQL language is supported as part of the SonarSource Developer Edition, which is a commercial package for which you need a license.
This is why if you install it manually, this will not work.
We are trying to upgrade our current SonarQube from 5.6.3. to 6.7.1
We have upgrade our SQL Server to 2014 and 5.6.3 has been tested and it has been working fine when I try to start the 6.7.1 server. It shows the Warning database needs an upgrade but the process seems to be running.
Is the issue because of the plugins which we are supporting or the version of database. I am attaching all the logs that got generated.
Database version : Microsoft SQL Server2014(MSSM studio 12.0.5207.0)
Plugin version :
SonarJava : sonar-java-plugin-4.6.0.8784
C# : sonar-csharp-plugin-5.10.1.1411
Does plugin version has to play any role ( I doubt as it is highly unlikely)
Let me know in case any further details are required.
Please advice.
Thanks in Advance!
It sounds like you're missing the step where you have SonarQube upgrade it's own database schema. Specifically, navigate to [your SonarQube URL]/setup and click the button on that screen. That triggers SonarQube to make the database changes required to support your new version.
is it possible to make the TFVC Plugin of SonarQube work with VSTS?
If I want to use the Plugin to connect with the TFVC of our VSTS-Account I get a not authorized exception. I'm pretty sure that the credentials are correct. Or Are there any special rights which are needed for that?
19:54:37.632 ERROR - Unable to TFS annotate the project which raised the following authentication exception: TF30063: You are not authorized to access xxx.visualstudio.com\DefaultCollection.
the configuration seems all correct, because the plugin works with a TFS2015-Server without any issues.
I'm Testing the plugin localy with the sonar Scanner V1.1.
SonarQube Version 5.2, TFVC Plugin Version 2.1
Thank you for your help!
Apparently this scenario is not supported yet. I ran into the same problem and I found the following issue on the backlog of the SonarQube team:
With the current TFVC Annotate plugin code author information is not seen for VSO hosted builds, this MMF is to enable the same.
You can find this information on: https://jira.sonarsource.com/browse/MMF-85
So until they fixed it I fear you'll need to disable this plugin...
Does anyone else have a problem where everytime you need to commit using the TeamCity VS plugin, you have to re-enter the TeamCity server address and credentials?
So should anyone stumble across this again - simple answer is to upgrade to the latest version! Worked for us.