This message was deleted.
# develocity
s
This message was deleted.
w
Can you check what the CI jobs are doing?
k
The CI workflow hasnt change and this is occurring on multiple projects, only on PRs that have the latest gradle enterprise plugin. Looking at a single CI run, all these phantom scans come after the last actual gradle command. This particular run had 4 scans which were expected and 35 scans that immediately followed.
None of these gradle executions are present in the raw logs from the job but the gradle-build-action is aware of them (and includes them in the job summary).
r
I see a
sonar
command around in your scans list... Are you using the sonarqube plugin version above 4.3 in those jobs? I faced exactly this issue in one of the latest versions some months ago. Reported here. You should downgrade the sonarqube plugin version to any released before this one https://community.sonarsource.com/t/gradle-scanner-v4-3-0-3225-launches-several-preparekotlinbuildscriptmodel-increasing-build-time/96250/1
k
Ah I was just testing reverting sonar because it was updated in our convention plugins along Gradle enterprise plugin. Thank you @Roldan Galan!
👍 1