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 <mark.ki...@gmail.com> 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 when doing releases. So if > > the Jenkins Sonar plugins reads this variable correctly, normally the > > Sonar run should not be skipped. So I think it's more of a Sonar > > plugin issue than a pure Sonar one. > > > > On Apr 23, 2:23 pm, Ann Campbell <ann.campb...@shawinc.com> wrote: > > > > > > > > > > > > > > > > > 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 contained in this > > > message. If you are not the addressee indicated in this message (or > are not > > > responsible for delivery of this message to that person) , you may not > copy > > > or deliver this message to anyone. In such case, you should destroy > this > > > message and notify the sender by reply e-mail. > > > If you or your employer do not consent to Internet e-mail for messages > of > > > this kind, please advise the sender. > > > Shaw Industries does not provide or endorse any opinions, conclusions > or > > > other information in this message that do not relate to the official > > > business of the company or its subsidiaries. > > > **********************************************************
