- versions used (SonarQube, Scanner, Plugin, and any relevant extension)
SonarQube Enterprise 7.6.0.21501
SonarQube Scanner 3.2.0.1227
SonarQube Scanner for Jenkins 2.8.1
- error observed (wrap logs/code around triple quote ``` for proper formatting)
PR-15500 shows this image:
With this text:
SonarQube Failed to check Code Quality
This is reported on the SonarQube server when I check background tasks for PR-15500:
java.lang.IllegalArgumentException: Multiple entries with same key: REDACTED:PULL_REQUEST:15500=ComponentImpl{type=FILE, status=ADDED, name='REDACTED', dbKey='REDACTED:PULL_REQUEST:15500', key='REDACTED', uuid='AWkmavhEgHOnJc9HB16f', description='null', children=[], projectAttributes=null, reportAttributes=ReportAttributes{ref=6862, path='null', scmPath='REDACTED/src/REDACTED/REDACTED.java'}, fileAttributes=FileAttributes{languageKey='java', unitTest=false, lines=31}} and REDACTED:PULL_REQUEST:15500=ComponentImpl{type=FILE, status=CHANGED, name='REDACTED', dbKey='REDACTED:PULL_REQUEST:15500', key='REDACTED', uuid='AWkmavhEgHOnJc9HB16f', description='null', children=[], projectAttributes=null, reportAttributes=ReportAttributes{ref=8896, path='null', scmPath='REDACTED/src/main/java/REDACTED.java'}, fileAttributes=FileAttributes{languageKey='java', unitTest=false, lines=62}}
at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:150)
at com.google.common.collect.RegularImmutableMap.checkNoConflictInBucket(RegularImmutableMap.java:104)
at com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:70)
at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:254)
at org.sonar.ce.task.projectanalysis.filemove.FileMoveDetectionStep.getReportFilesByKey(FileMoveDetectionStep.java:186)
at org.sonar.ce.task.projectanalysis.filemove.FileMoveDetectionStep.execute(FileMoveDetectionStep.java:113)
at org.sonar.ce.task.step.ComputationStepExecutor.executeStep(ComputationStepExecutor.java:77)
at org.sonar.ce.task.step.ComputationStepExecutor.executeSteps(ComputationStepExecutor.java:69)
at org.sonar.ce.task.step.ComputationStepExecutor.execute(ComputationStepExecutor.java:56)
at org.sonar.ce.task.projectanalysis.taskprocessor.ReportTaskProcessor.process(ReportTaskProcessor.java:81)
at org.sonar.ce.taskprocessor.CeWorkerImpl.executeTask(CeWorkerImpl.java:137)
at org.sonar.ce.taskprocessor.CeWorkerImpl.findAndProcessTask(CeWorkerImpl.java:100)
at org.sonar.ce.taskprocessor.CeWorkerImpl.withCustomizedThreadName(CeWorkerImpl.java:84)
at org.sonar.ce.taskprocessor.CeWorkerImpl.call(CeWorkerImpl.java:76)
at org.sonar.ce.taskprocessor.CeWorkerImpl.call(CeWorkerImpl.java:46)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
- steps to reproduce
This does not happen consistently, but does happen frequently on PR scans. There are a lot of PR scans that overlap in time.
- potential workaround
None known at this time. I’m seeing if rerunning the pipeline in Jenkins resolves it. It happens frequently enough that this is not a viable workaround long-term.