sonarqube5.1 - SonarQube 5.1 fails execution with message "The project already being analyzed" -


we have had occurrences sonarqube job running hours, appears hung no eta on completion in our ci environment. have used workaround solution of not aborting build job, there seems secondary process executing sonarqube on ci agent itself. have read specifying sonar.forceanalysis=true should resolve issue has been deprecated of version 3.x , there no need use analysis parameter. able proactively address , not have respond after team running sonarqube notifies of issue. there way of specifying timeout process running analysis terminate?

if looking killing analysis running in ci environment after time, suggest feature offered ci environment.

there no such thing in sonarqube.

as side note, should have upcoming 5.2 release of sonarqube. have cut connection database analyzer means error “the project being analyzed” can not occur more. in addition, quite bunch of work done analysis job has been moved server allow run faster.


Comments

Popular posts from this blog

php - Invalid Cofiguration - yii\base\InvalidConfigException - Yii2 -

How to show in django cms breadcrumbs full path? -

ruby on rails - npm error: tunneling socket could not be established, cause=connect ETIMEDOUT -