Missed github notification bug

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube 9.4.0-developer, official dockerized release, Plugins are:
checkstyle-sonar-plugin-9.2.1.jar
qualinsight-sonarqube-smell-plugin-4.0.0
sonar-cobertura-plugin-2.0
sonar-findbugs-plugin-4.0.5
sonar-groovy-plugin-1.8
sonar-pmd-plugin-3.3.1
sonar-prometheus-exporter-1.0.0
sonar-yaml-plugin-1.7.0

and any relevant extension)

  • what are you trying to achieve
    Assure gitlab MergeRequest gets analysis notification when sonarqube completes

  • what have you tried so far to achieve this
    Logs in Jenkins CI show:

[2022-06-14T12:40:38.600Z] [INFO] Analysis report generated in 459ms, dir size=13.1 MB
[2022-06-14T12:40:41.828Z] [INFO] Analysis report compressed in 3046ms, zip size=5.6 MB
[2022-06-14T12:40:42.379Z] [INFO] Analysis report uploaded in 963ms
[2022-06-14T12:40:42.379Z] [INFO] ANALYSIS SUCCESSFUL, you can find the results at: https://<REDACTED>ffs-parent&branch=sonarqube-2022
[2022-06-14T12:40:42.379Z] [INFO] Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report
[2022-06-14T12:40:42.379Z] [INFO] More about the report processing at https://<REDACTED>/api/ce/task?id=AYFiOv0lMeSggZqRhsNP
[2022-06-14T12:40:43.290Z] [INFO] Analysis total time: 3:15.450 s
[2022-06-14T12:40:43.291Z] [INFO] ------------------------------------------------------------------------
[2022-06-14T12:40:43.291Z] [INFO] Reactor Summary for FFS Parent 10.1.0-SNAPSHOT:

While the CE log in SonarQube shows:

2022.06.14 12:41:12 INFO  ce[AYFiOv0lMeSggZqRhsNP][o.s.c.t.s.ComputationStepExecutor] Trigger refresh of Portfolios and Applications | refreshesAPP=0 | status=SUCCESS | time=2ms
2022.06.14 12:41:12 INFO  ce[AYFiOv0lMeSggZqRhsNP][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Webhooks | globalWebhooks=0 | projectWebhooks=0 | status=SUCCESS | time=2ms
2022.06.14 12:41:12 INFO  ce[AYFiOv0lMeSggZqRhsNP][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Pull Request decoration | status=SUCCESS | time=0ms
2022.06.14 12:41:12 INFO  ce[AYFiOv0lMeSggZqRhsNP][o.s.c.t.p.a.p.PostProjectAnalysisTasksExecutor] Report branch Quality Gate status to devops platforms | status=SUCCESS | time=1ms
2022.06.14 12:41:12 INFO  ce[AYFiOv0lMeSggZqRhsNP][o.s.c.t.CeWorkerImpl] Executed task | project=com.digitalsmiths.ffs:ffs-parent | type=REPORT | branch=sonarqube-2022 | branchType=BRANCH | id=AYFiOv0lMeSggZqRhsNP | submitter=sonar | status=SUCCESS | time=29088ms

But the Web log in SonarQube shows:

2022.06.14 12:44:47 INFO  web[][o.s.a.c.g.GitlabHttpClient] Gitlab API call to [https://git.digitalsmiths.com/api/v4/projects] failed with error message : [connect timed out]
java.net.SocketTimeoutException: connect timed out
	at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412)

Hey there.

This API call being made by the web process would be used in the scenario of project onboarding (creating a new project from a GitLab repository) rather than performing PR decoration. We can set that aside for now.

It looks like Branch analysis is being performed rather than Pull Request Analysis. Are you sure the pipeline is running in the context of a Pull Request, and how is your Jenkins job configured?

Sorry; going into this I probably should have mentioned that the connectivity from sonarqube on AWS to the client host is blocked by changed firewall rules since they were originally setup. I was just pointing out that the PR-decoration (this is a Gitlab Merge-Request) should have shown as failed.

Hey there.

It probably would have… if a Pull Request Analysis had actually been run. However, this was a branch analysis, where no PR decoration took place (although we log something in the CE, it’s just skipped immediately since it’s not a PR analysis)

I’ll look back in the logs to see if I can identify the appropriate build info.

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