Re: Log file for SONAR-3232

Hi Freddy,

Just rechecked our nightly jobs. Of course there are parallel sonar
analysis as we have a few hundreds CI jobs but these are all different
projects with different name/artifactId. They have the same parent pom
though which must not be a problem.

I'm pretty positive that we do not have parallel runs of the same project.

Re: Log file for SONAR-3232

Hi Yves,

I'm sorry to come back with the same explanation but each time this issue was encountered this was always for the same reason : parallel analysis on the same project or ... on a project and on one of its module.

Just rechecked our nightly jobs. Of course there are parallel sonar analysis as we have a few hundreds CI jobs but these are all different projects with different name/artifactId. They have the same parent pom though which must not be a problem.

I'm pretty positive that we do not have parallel runs of the same project.

Any other known use case that can cause this problem?

Regards,
Yves

On 02.07.2012 21:55, Freddy Mallet wrote:

Hi Yves,

According to your last comment on SONAR-3231 ticket, this failure is due
to some parallel analysis on the same Sonar project and this is a known
Sonar limitation.