was not able to fetch data for Sonar project com.sgx.bt.tsnext:feature/BT-4662
RFQ_CHANGES_FOR_ALERTS".
Either your pull request has not been analyzed yet, a non-existing Sonar project is referenced, you use the new branching feature of SonarQube 6.7 but haven't enabled this in the repository settings or you have upgraded Sonarqube without restarting the plugin
(disabling and re-enabling in the UPM ). you can configure the sonar project in the
repository settings
Hi,
It looks like the plug-in wasn't able to find Sonar results for this branch. Could you please make sure that there is a project with this branch in SonarQube? If there is, please create a support request in our service desk so that we can analyze this in more detail (maybe by exchanging debug logs).
Thanks,
Michael from Mibex Software
I am also facing similar issue, I am having a develop branch and from there we create feature branch and once code is done. we merge from feature --> develop branch.
Above error encountered when I am having analysis published for develop branch and now i am trying to create a pull request from feature to develop.
Does it means that I need sonar analysis for feature branch needs to be available to get results ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@priyang patelExactly, the feature branch needs to be analyzed as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So this plugin needs both develop and feature branch analyzed before we create pull request Correct ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Technically, the feature (source) branch of the pull request is enough when you use "Leak Period" mode. If you use "Branch-based" mode, then both branches need to be analyzed. It depends a bit if you want to use "Leak Period" or not (requires you to configure sonar.projectVersion). Does that help you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have disabled branch based mode and enabled leak period, still getting below error.
Was not able to fetch data for Sonar project "AAA:develop:Feature/abc_1". Either your pull request has not been analyzed yet, a non-existing Sonar project is referenced, you use the new branching feature of SonarQube >= 6.7 but have not enabled this in the repository settings or you have upgraded SonarQube without restarting the plug-in (disabling and re-enabling in the UPM). You can configure the Sonar project in the
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One more question
We are having around 50+ visual studio solutions in my repository , I am creating separate 50 projects in sonarqube for a feature branch. Now when a developer commit changes he /she commit against the same repository and they will create only one pull-request. Now that pull request could have code for multiple solutions (and multiple projects in sonar). for this situation how are you suggesting to configure this utility.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess your project key is "AAA". Could you please make sure that you have "AAA" in the field "Project base key" in the repository settings of the plug-in?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes , key is present in project base key.
But one thing I want to understand, in any case feature (source) branch , from where I am creating pull request to merge to develop branch, needs to be analyzed first to use this plugin ?
In short source branch needs to be analyzed and published to soanr server before we create pull request.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's correct, the source branch needs to be analyzed first. Could you please make sure that your project base key is exactly "AAA", but not "AAA:develop"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure , The constraint what we are having is we cant publish statistics for "feature" branch in advance , as we are using one common instance for whole organization and there are constraints which is stopping us to send feature file statistics to sonar instance.
Just want to understand that your tool is internally fetching details from sonar server for the source branch and show to bit bucket. Its not generating and showing new debt on runtime.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.