Do not run sonar analysis from integration honeycomb jobs

No need, sonar analysis is run on merge jobs. No need to run again
from integration job. Also integration jobs might be run even if honeycomb
code hasen't changed, running the analysis pointlessly.

Change-Id: I527dbc77e9ce528da169443a77f47f5251216670
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>

diff --git a/jjb/honeycomb/honeycomb.yaml b/jjb/honeycomb/honeycomb.yaml
index 386fb21..55f0681 100644 (file)
--- a/jjb/honeycomb/honeycomb.yaml
+++ b/jjb/honeycomb/honeycomb.yaml
@@ -259,7 +259,7 @@
     maven:
         maven-name: '{mvn33}'
         root-pom: 'pom.xml'
-        goals: 'clean install -V -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r  -Dmerge -Dkaraf.keep.unpack=true -Dsonar'
+        goals: 'clean install -V -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r  -Dmerge -Dkaraf.keep.unpack=true'
         maven-opts: '-Xmx2048m -Dmaven.compile.fork=true'
         settings: 'honeycomb-settings'
         settings-type: cfp
@@ -288,9 +288,6 @@
         - findbugs
 
     publishers:
-        - sonar:
-            language: 'java'
-            branch: '{stream}'
         - email-notification:
             email-prefix: '[honeycomb]'
         - maven-deploy: