[JENKINS-29628] createVariableResolver() is called with null as a parameter

createVariableResolver() method in FilterScript.java (97) is called with null as a parameter instead of build instance.

final String value = pv.createVariableResolver(null).resolve(name);

This is against specification

http://javadoc.jenkins-ci.org/hudson/model/ParameterValue.html#createVariableResolver(hudson.model.AbstractBuild)

where we can read that:

build - The build for which this parameter is being used. Never null.

This null is causing other plugins to fail. For example:

https://issues.jenkins-ci.org/browse/JENKINS-29539

---
Originally reported by zuljin, imported from: createVariableResolver() is called with null as a parameter

• assignee: kohsuke
  
• status: Open
  
• priority: Critical
  
• component(s): matrix-project-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 2025-12-06
  

Raw content of original issue

createVariableResolver() method in FilterScript.java (97) is called with null as a parameter instead of build instance.

final String value = pv.createVariableResolver(null).resolve(name);


This is against specification

http://javadoc.jenkins-ci.org/hudson/model/ParameterValue.html#createVariableResolver(hudson.model.AbstractBuild)

where we can read that:

build - The build for which this parameter is being used. Never null.


This null is causing other plugins to fail. For example:

https://issues.jenkins-ci.org/browse/JENKINS-29539

Start in FilterScript.java at the createVariableResolver(null) call shown in the issue, then inspect how the build instance is available in that code path. Compare the call with the ParameterValue.createVariableResolver specification and verify the affected variable-resolution scenario no longer receives null.

Written by the indexing model from the issue text.