Fix sonar jobs due to freestyle transition 01/45501/2
authorThanh Ha <thanh.ha@linuxfoundation.org>
Mon, 12 Sep 2016 17:18:15 +0000 (13:18 -0400)
committerThanh Ha <thanh.ha@linuxfoundation.org>
Mon, 12 Sep 2016 17:35:05 +0000 (13:35 -0400)
commitd94f468d77a778b7ec50a08595587ef6b2f30cc1
tree42e19ccd94de87b866e759fe964975e4f8db8bbe
parentce00c3413739277f6b7d674a5ae7dcb62b15b43a
Fix sonar jobs due to freestyle transition

The freestyle job migration from patch
I810316417769df3c4f3f775aff3f3c151be76e3f broke the sonar jobs due to
missing jdk and maven-version configuration. Unfortunately JJB does not
support configuration those options either.

Since the post build step for Sonar is deprecated anyway there's no
point continuing to use it so transition to using the sonar method
recommended by SonarQube [0].

The "Prepare SonarQube Scanner environment" is currently not
configurable via Jenkins so explicitly set the Maven Goals directly to
work around this. We should switch back in the future once JJB supports
the setting.

[0]
http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Jenkins

Change-Id: I6a3e00c4b385adad03a470d3aae0e476c6bb769d
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
jjb/netvirt/netvirt-sonar.yaml
jjb/ovsdb/ovsdb-sonar.yaml
jjb/releng-templates-java.yaml