Is it always safe to define sonar.forceAnalysis=true for SonarQube analysis? -


when parallel sonarqube analyses started, 1 rejected / fail error: the project being analysed.

i learned on mailing list entry possible override check adding --define sonar.forceanalysis=true apache maven command.

thus (to repeat title): always safe define sonar.forceanalysis=true sonarqube analysis?

why care / ask?

  1. i know interesting corner cases or concerns using flag. examples: there downsides or risks? corrupt sonarqube database?
  2. i have teamcity cloud multiple build agents. if more 1 agent triggers build (after multiple, successive version control commits), sonarqube analyses may overlap.

this property deprecated since sonarqube 3.5 , no longer necessary. see http://docs.sonarqube.org/display/sonar/frequently+asked+questions#frequentlyaskedquestions-failedtoanalyseaprojectasanotheranalysisonthesameprojectseemstoberunningatthesametime(sonarqube3.4only)


Comments

Popular posts from this blog

android - MPAndroidChart - How to add Annotations or images to the chart -

javascript - Add class to another page attribute using URL id - Jquery -

firefox - Where is 'webgl.osmesalib' parameter? -