Groovy判空疑问：Jenkins流水线用‘null’字符串判断为何有效？

Great question! Let’s unpack why your current null-check code is working as expected, even though it looks counterintuitive at first glance.

The Root Cause: Jenkins Pipeline Variable Behavior #

In Jenkins Pipelines (especially when dealing with build parameters, environment variables, or values passed from external sources), unset or empty values are often converted to the string "null" instead of Groovy’s actual null reference.

For example:

• If you leave an optional build parameter environment blank during a run, Jenkins might not pass a null object to your pipeline—it passes the literal string "null" instead.
• This is a key quirk of how Jenkins handles unconfigured values, different from standard Groovy where an uninitialized variable would be null.

Why Your Current Code Works #

Let’s break down the differences between your approach and the one you initially thought was correct:

• Your existing code: if (environment != 'null') { envPlatformArray.add(environment) }
  • This explicitly filters out the string "null", which is exactly what Jenkins is passing when the value isn’t set. If you used if (environment != null) instead, it would let the string "null" slip through (since "null" is a valid non-null String object), which would trigger Xray’s exception.
• The approach you assumed was right: if (environment) { ... }
  • In Groovy, non-empty strings are truthy—so the string "null" would evaluate to true, causing you to add the invalid "null" value to your array. That’s exactly what you don’t want for Xray!

How to Verify This #

To confirm what’s happening with your variables, add a quick debug line to your pipeline:

echo "environment type: ${environment.getClass()}, value: '$environment'"

If the output looks like environment type: class java.lang.String, value: 'null', that confirms you’re dealing with a string literal "null" rather than a null object.

When to Adjust Your Check? #

• Stick with != 'null' if Jenkins consistently passes "null" for unset values in your pipeline—it’s perfectly adapted to your current setup.
• If you ever switch to a scenario where variables are actual null references (e.g., setting variables programmatically in Groovy), then if (environment != null) or if (environment) would be appropriate—but only if you’re sure empty strings or "null" strings aren’t in play.

内容的提问来源于stack exchange，提问作者Huibin Zhang