Sonarqube 7

0 views

Skip to first unread message

Alethia Tiell

unread,

Aug 3, 2024, 2:08:52 PM8/3/24

to mangewordta

I have now upgraded by Sonarqube instance in DEV test environment from 7.9 to 8.9 LTS and was wondering why there is no plugins installed in conf/extensions/plugins and when i tried to copy across from old version Sonarqube was unable to start up. Attached upload shows current plugins in 7.9

take a look at the post here for explanation.
the language analyzers from sonarsource are now shipped with each release and the directory in question is only for 3rd party plugins. This change was introduced with sonarqube 8.5

So, I started up with an empty directory and reinstalled from the UI, to then also curse wondering "Where did all the language plugins in the Marketplace go? My concern with approach is any custom settings may disappear if the plugin were not present.

Does that mean we can only expect plugin updates and rules updates as part of an incremental LTS release and does that imply there will be MORE minor LTS releases just to get updated (Non-) language plugins and rules ? Seem like overkill.

Hello to all
I need to update my sonarqube developer edition from version 7.9.1 to version 8.1.
I saw as suggested by the app that to proceed with the migration I have to go for the intermediate LTS versions. I then made the transition from 7.9.1 to 7.9.2 LTS without problems, but if I then try to start version 8.1 it still tells me of the docker logs that:

Also note that we dropped the support of MySQL starting from SonarQube 7.9, so I am very surprised that you could run SonarQube 7.9.1 or 7.9.2 with MySQL in the back-end. Are you sure this is the DB you use ?

I can see that both 8.9.4 and 9.2.2 are still using 2.11.1 for log4j in elastic search instead of 2.16.0 .However I have noticed in es log that they have added -Dlog4j2.formatMsgNoLookups=true to 8.9.4 .In earlier versions -Dlog4j2.formatMsgNoLookups=true property need to be set via sonar.properties

If I am not wrong , they have only added sonar.search.javaAdditionalOpts=-Dlog4j2.formatMsgNoLookups=true to these versions which we can see in es log. As you mentioned still old 2.11.1 jars are available with this new released version.

I am using the HELM chart and DOCKER image to deploy sonarqube, and I am trying to change the deployment in such a way that I do not need to edit the values.yaml file. I am trying to use the --set env option as documented in the chart on github but I cannot find the correct syntax to make it work.

However, if I perform an interactive login into the container and check /opt/sonarqube/conf/ and cat the file, the config option mentioned above is commented out. Should that not be set in this image?

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 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.

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.

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.

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.

Prior to the Semester, the instructor should contact req...@divms.uiowa.edu and request a subgroup of clas-sonarqube be created for the class in research-git.uiowa.edu ( e.g. clas-sonarqube/cs-XXXX-20XX-Fall). The instructor will then be able to create subgroups (sonarqube/cs-XXXX-20XX-Fall/team_1) and assign members and permissions to that class. All of the git projects created under these subgroups will have access to the gitlab-runner provided by sonarqube. Everyone will need to log in to -git.uiowa.edu at least once before permissions can be added.