Just out of curiosity - you run a sonar check with ever build?
If you agree that is overkill, set up a @midnight sonar job for everything
you want a health check on. Are you doing this in order to leverage the
build breaker plugin?
On Monday, April 23, 2012 8:37:48 AM UTC-4, Mark Kiami wrote:
Sorry I meant, the Sonar run "should be skipped"... (not "should not
be skipped")
On Apr 23, 2:36 pm, Mark Kiami wrote:
> For info, I tried a pre-build shell task with an echo of the
> IS_M2RELEASEBUILD variable, as well as a post-build shell task, they
> both print "true" for the variable value
For info, I tried a pre-build shell task with an echo of the
IS_M2RELEASEBUILD variable, as well as a post-build shell task, they
both print "true" for the variable value when doing releases. So if
the Jenkins Sonar plugins reads this variable correctly, normally the
Sonar run should not be skipped
Sounds like you're doing it right. You probably want to re-ask this at the
Sonar user list. You'll need to subscribe first:
http://www.sonarsource.org/support/support/
:-/
Ann
>
--
**
Privileged and/or confidential information may be
I am using the Sonar Jenkins plugin, and would like to skip Sonar when
performing a maven release.
To do that I have a variable called "IS_M2RELEASEBUILD" in "Release
envrionment variable" and I am using that same variable name in the Sonar
advanced field called "Skip if environment variable is
