-
Notifications
You must be signed in to change notification settings - Fork 18
Issue when pushing to upstream branch due to OverlappingFileLockException #94
Comments
Hi, I've never run into this issue before, but it would useful if you could you share a stack trace. I'm curious to see where this exception originates from. |
I'm running into the same issue. My sbt project has 18 subprojects and is running in gitlab-ci. I only get this exception on 5 of the subprojects. Not all of them. Is there a way to run sonarScan sequentially opposed to concurrently? Here's my stacktrace:
|
Hi, yes - what you probably want to do is to define an aggregate project across all of your subprojects and trigger the |
Yes, makes sense. We'll give that a shot. Thanks for the speed response! |
Hi,
I am currently working on implementing SonarQube quality gates on the pipelines of multiple projects to ensure that it's not possible to push code upstream or merge to master unless the new code is covered by tests. I am running
sonarScan
against an aggregate project that contains all of the projects to be assessed, and there is a sonar scan stage in the pipeline that performs that check.The current implementation of the quality gate runs sonar scan against all projects separately, as well as against an aggregated project that is used for the gate check. Currently there is an issue that is occurring on the pipeline where running sonarScan results in an OverlappingFileLockException It runs sonarScan against all of the projects in the aggregated project, and this error is thrown on the second project, regardless as to which project this is.
Any help on this matter would be much appreciated.
The text was updated successfully, but these errors were encountered: