3 # Install and run SonarQube on travis.
5 # Use it as a wrapper to your build command, eg: ./travis-sonarqube.sh make VERBOSE=1
7 # On Mac OSX or with pull requests, you don't want to run SonarQube but to exec the build command directly.
9 # Be verbose and fail fast
12 # Install required software
13 installSonarQubeScanner() {
14 export SONAR_SCANNER_HOME=$HOME/.sonar/sonar-scanner-2.8
15 rm -rf $SONAR_SCANNER_HOME
16 mkdir -p $SONAR_SCANNER_HOME
17 curl -sSLo $HOME/.sonar/sonar-scanner.zip http://repo1.maven.org/maven2/org/sonarsource/scanner/cli/sonar-scanner-cli/2.8/sonar-scanner-cli-2.8.zip
18 unzip $HOME/.sonar/sonar-scanner.zip -d $HOME/.sonar/
19 rm $HOME/.sonar/sonar-scanner.zip
20 export PATH=$SONAR_SCANNER_HOME/bin:$PATH
21 export SONAR_SCANNER_OPTS="-server"
23 installBuildWrapper() {
24 curl -LsS https://sonarcloud.io/static/cpp/build-wrapper-linux-x86.zip > build-wrapper-linux-x86.zip
25 unzip build-wrapper-linux-x86.zip
27 installSonarQubeScanner
30 # triggers the compilation through the build wrapper to gather compilation database
31 ./build-wrapper-linux-x86/build-wrapper-linux-x86-64 --out-dir bw-outputs "$@"
33 # Run ctest before sonar to gather coverage some information
35 ctest --output-on-failure
39 # Only run sonar on master (not on pull requests)
40 if [ "$TRAVIS_PULL_REQUEST" != "false" ] ; then
44 # generate the gcov files
45 ctest -D ExperimentalCoverage
47 # and finally execute the actual SonarQube analysis
48 # (the SONAR_TOKEN is set from the travis web interface, to not expose it with an ongoing "set -x")
49 # See https://docs.travis-ci.com/user/sonarqube/ for more info on tokens
50 # don't show the token in the logs
52 sonar-scanner -Dsonar.host.url=https://sonarcloud.io -Dsonar.login=$SONAR_TOKEN 2>&1 \
53 | grep -v 'INFO: Parsing /home/travis/build/simgrid/simgrid/Testing/CoverageInfo' \
54 | grep -v 'WARN: File not analysed by Sonar, so ignoring coverage: /usr/include/'