"Skip if environment variable is defined" doesn't work for environment variable

We are doing something similar here, where we compute the value of SKIP_SONAR variable depending on a number of different criteria. The value is set by the EnvInject plugin and is indeed the right value. However, Sonar keeps executing even though we have configured it to skip running if SKIP_SONAR is set...

The only way this works for us is if SKIP_SONAR is defined as a build parameter. Anything else fails to trigger the expected behavior from Sonar, i.e. to skip it when we don't want it to run. This is obviously not enough.

Sorry, I forgot to describe our setup.

• Jenkins LTS 1.447.2
• Sonar Plugin 1.8.
• Maven 3.0.4

I have similar situation however not even defining a Boolean Parameter named "NO_SONAR" is working for me.

I've tested running the build manually having the parameter "NO_SONAR" (the same as defined in System Configuration), being by default enabled (set to "true").

Job is configured to with "Invoke Standalone Sonar Analysis" as build step.

My system is:

• Jenkins ver. 1.482
• Jenkins Sonar Plugin 1.8

The problem was that only build parameters were considered. I have commited a fix to also take environment variables into account.

@Jose I don't understand your point because "Skip if environment variable is defined" is only available with post build action and not with "Invoke Standalone Sonar Analysis" as build step.

Manually tested.

What I meant is that it is possible to run Sonar in job in 2 places. As a Build step named "Invoke Standalone Sonar Analysis" and as a post-build action named just "Sonar".

You can find attached a sample job definition that has both and the workaround for the build step using "Conditional Build Step" plugin to check the build parameter and skip the sonar execution if the parameter "SKIP_SONAR" is set to true.

For this to work, either case should no run if the parameter was set to true, but just using the build step without the Conditional additional check runs it either way.

test_sonar.xml job definition: http://pastebin.com/uXRVFkXc
test_sonar execution output: http://pastebin.com/j6w4WeVF

The "Invoke Standalone Sonar Analysis" uses Sonar runner 1.2 (when do you upgrade to 2.0?) while the post-build action "Sonar" uses only Maven method.

Could you please use the sonar user mailing list for this kind of question.

It seems you encounter an issue with Conditional Build Step that at first seems not related to Jenkins Sonar plugin (as I said standalone sonar analysis build step has no built-in skip feature).

I would send it to mailing list if I knew what it was and I don't see any mentioned in http://docs.codehaus.org/display/SONAR/Hudson+and+Jenkins+Plugin. care to provide that info ?

I think this is a lack of consistency issue. When you have in Jenkins System Configuration the options specific for this plugin the possibility to like indicated in the title of this issue to "Skip if environment variable is defined", I would expect that all possible executions of this plugin would behave consistently in the same manner, which is to skip the build if the environment variable "SKIP_SONAR" being defined as a Boolean parameter in the job itself is set to true. Since it has no indication in its documentation this only works with the pos-build step "Sonar" specific only to maven I assumed it was also applicable to the Standalone build step.

Regarding Conditional Build Step plugin, there is no issue with. That is actually the Workaround I found that overcomes this Problem on the Standalone Sonar Analysis build step because it was not behaving as expected. In my opinion the use of this plugin would not be needed if the Plugin had consistent behavior.

The test_sonar.xml I've indicated above is an example of such, just copy it to your instance, run it and you'll see the problem.

It is the expected behavior that the sonar build step is not skipped since the "Skip if environment..." parameter only applies to the post job Sonar action (we tried to make it more clear in SONARPLUGINS-1719). We will not implement a skip mechanism for the build step especially because as you said there is an existing plugin to do the same in a consistent way for all kind of build steps.
If you disagree with this point of view feel free to open a discussion on user mailing list (http://docs.codehaus.org/display/SONAR/Mailing-lists).

Concerning the update to Sonar Runner 2.0 this was addressed by SONARPLUGINS-2126. The vote has been started on the dev mailing list (http://sonar.15.n6.nabble.com/sonar-dev-VOTE-Jenkins-Hudson-Sonar-Plugin-2-0-td5004051.html).