No analysis results showing up in IntelliJ IDEA after plugin update

SonarQube for IDE IntelliJ Platform
1
  • Operating system: Windows 11
  • SonarLint plugin version: 10.13.1.80133
  • IntelliJ version: IntelliJ IDEA 2024.3 (Ultimate Edition), Build #IU-243.21565.193
  • Programming language you’re coding in: Java
  • Is connected mode used:
    • Connected to SonarQube (v9.9.7 (build 96285))

And a thorough description of the problem / question:

I’m clicking “Analyze VCS Changed Files” in the “Report” tab. After the analysis, the prompt “Trigger an analysis…” is still displayed instead of the analysis results.

Here is the verbose log. I hope I didn’t redact too much.
SonarQubeIDE.txt (402.9 KB)

Thank you very much in advance!

2

Hey @mkomko, thanks for reaching out to us, that is effectively strange. We can see the issues are raised in the logs.

Do you have multiple IDEs open at the same time? Have you triggered multiple analyses while they were running? Also, do you still see a background task running in the taskbar?

5

Yes. No. No.

6

So I have experimented some more. I upgraded IntelliJ to 2024.3.1 as well.
Analysis seems to only work in the IDE project/window that is opened first.

7

Could you share more information on your project structure, is it a monorepo?

8

Our project consists of multiple modules with dependencies on each other. It’s a Jakarta EE/JSF project with an EJB module, a WEB module and other modules. They are all in a single repository.

I have it checked out from Git in multiple directories, so I can work on multiple branches at the same time. So both open IntelliJ projects are the “same” project, but in different directories.

9

It seems to be related to the “same” project being open multiple times. If I open a different project in a third window, it can be analyzed.

10

Yes, this is likely the source of the issue, as we rely on the module’s names to find the right IntelliJ window.

I created this bug ticket and I’ll try to see what we can improve on this.

11

Thank you! It’s a regression, since it worked before the latest plugin update, so I hope it will be fixed. I’ll mark your reply as solution.

1 Like
12

It’s a regression, since it worked before the latest plugin update

AFAIK, it has been an issue forever. I also reproduced the issue in the previous version (10.12). Are you sure you have not experienced this problem before?

13

I have been using it that way for a very long time. Sure, there were times where I had problems, but most of the time these could be connected to other bugs.
But no, I can’t be absolutely sure, so you’re probably right, my apologies. You know the code and the product much better than I do, I’m sure :slight_smile:

1 Like
15

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.