X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/2b93372d5968f244e791359c1f9b8692f4d2c2b1..daacb576495293505af7107b9acfbe1eb143d897:/tools/internal/travis-sonarqube.sh

diff --git a/tools/internal/travis-sonarqube.sh b/tools/internal/travis-sonarqube.sh
index c54b798ecf..3dc02e584a 100755
--- a/tools/internal/travis-sonarqube.sh
+++ b/tools/internal/travis-sonarqube.sh
@@ -1,6 +1,19 @@
 #! /bin/sh
 
-# Run SonarQube on travis. First version was given per email by one of the SonarQube engineer.
+# Install and run SonarQube on travis. 
+#
+# Use it as a wrapper to your build command, eg: ./travis-sonarqube.sh make VERBOSE=1
+
+# On Mac OSX or with pull requests, you don't want to run SonarQube but to exec the build command directly.
+if [ ${TRAVIS_OS_NAME} != 'linux' ] || [ ${TRAVIS_PULL_REQUEST} != 'false' ] 
+then
+  exec "$@"
+fi
+# Passed this point, we are on Linux and not in a PR (exec never returns)
+
+
+# Be verbose and fail fast
+set -ex
 
 # Install required software
 installSonarQubeScanner() {
@@ -21,7 +34,8 @@ installSonarQubeScanner
 installBuildWrapper
 
 # triggers the compilation through the build wrapper to gather compilation database
-./build-wrapper-linux-x86/build-wrapper-linux-x86-64 --out-dir bw-outputs make all
+./build-wrapper-linux-x86/build-wrapper-linux-x86-64 --out-dir bw-outputs "$@"
 
 # and finally execute the actual SonarQube analysis (the SONAR_TOKEN is set from the travis web interface, to not expose it)
+# See https://docs.travis-ci.com/user/sonarqube/ for more info on tokens
 sonar-scanner -Dsonar.host.url=https://nemo.sonarqube.org -Dsonar.login=$SONAR_TOKEN