I am trying to integrate Jira with SonarQube. I used "SonarQube connector for JIra" for that. Now the problem is I have more than 2000 projects created on SonarQube server based on the structure of the repository.
I have only few High Level Jira projects created to which multiple sonarQube projects are linked.
I know providing the comma separated list of sonarQube projectKeys in the SonarQube connector settings page on Jira project.
My question is, Is there a limit on the number of projects can be linked to each Jira project.???
Hello @vsk csr , thank you for your question and for your interest in our product.
Remember that you can use tags instead of writing the resource ids one by one.
On the other hand, the sonarqube connector for jira is tested with around 100 projects configured for a single jira project with an optimal result.
Take into account that, the greater the number of projects, the greater the number of issues, of queries to the API... which can make the response time of the connector not optimal.
If you need help with any other topic, do not hesitate to contact us: excentia portal
Greeting.
I tried to link around 110 projects.
but i am able to do it for 87 SonarQube projects to one Jira project.
I like the idea to link issues using their tags.
but my question regarding ‘tags’ is…
How do we map the issues related to the desired projects only.
i don’t want all the issues with specified tag to be showing up.
i want that list to be narrowed down to the selected SonarQube projects only.
thanks
vsk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @vsk csr ,
I mean use tags for sonarqube projects so that you don't have to write all the project keys separated by commas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carlos,
could you please share any information related to “linking SonarQube projects to jira project using tags”.
i am little confused here. Because, if we use sonarqube issue tags linked to jira project, that jira project is going to have the issues from all the projects with that specified tag from that SonarQube instance.
but here i want to see the issues of only specific number of SonarQube projects to be linked to Jira proejct.
please let me know how to get this done.
thanks
vsk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @vsk csr ,
I am not talking about issue tags, I am talking about sonarqube project's tags.
For your convenience, if you are going to configure a large number of projects, instead of adding your resource keys one by one, you can tag these projects in sonarqube.
So then, in our connector you would only have to configure the Tags field by writing a single tag and you will see the issues of only those specific number of SonarQube projects.
Best regards!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carlos,
As you said, I started using SonarQube projects tags to map them to Jira Projects.
It is good until certain number of Jira projects. Let's say around 10-150 projects.
I tested to attach only 1 tag which is assigned to around 200 sonarqube projects.
Now the issue is...
I have a tag assigned to around 200 sonarqube projects.
But it is giving me the following error
"
Error during plugin execution: please contact your Administrator. Cause: Error 414 on https://codereview.cmicglobal.com/api/issues/search?componentKeys="all the projectKeys are listed here &facets=severities&resolved=false : <html> <head><title>414 Request-URI Too Large</title></head> <body> <center><h1>414 Request-URI Too Large</h1></center> <hr><center></center> </body> </html>
"
I guess there is limit for the url length.
Please confirm what is the maximum length allowed.
OR
Is there any maximum number of SonarQube projects can be linked/mapped to a Jira Project?
Please confirm if if there is a limit of maximum number of projects assigned with a single tag?
Just FYI,
Instead of trying with a single project tag for all the 200 projects, I have categorized based on the project type. Now I have around around 50 tags.
Now I am able to map around 175 projects which are linked with around 38 tags.
Basing on this, I presume there is a limitation of number of SonarQube projects that can be mapped to a single Jira project.
Please provide a solution for this.
Thanks in advance
vsk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @vsk csr
The limitation occurs from part of the SonarQube server, or from the proxy in front of it.
If the project keys are very long then this problem may occur, you should check with the systems staff what limit is configured and then configure the plugin knowing more or less what the limit will be.
For example, in Windows by default it can cause these types of problems. In the SonarQube documentation you can see the reference to what I mean:
https://docs.sonarsource.com/sonarqube/9.9/setup-and-upgrade/configure-and-operate-a-server/operating-the-server/#using-iis-on-windows
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, @vsk csr — welcome the community 👋
I wonder if you might have better luck posing this question directly to excentia.
There are only 1K downloads of SonarQube Connector for Jira, and we can assume not all of those are actively used. That means the likelihood of there being an active Atlassian Community member who knows the answer to your questions is probably very small.
I hope this helps,
-dave
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.