[JENKINS-10779] Non-existing parameters are not empty but replaced with parameter name

Version

• Jenkins Parameterized Trigger plugin 2.11


• Jenkins ver. 1.424

Setup

1. Project1 is set up to trigger parameterized build on Project2 with parameter

   SOURCE_JOB_NAME=$JOB_NAME



2. Project2 is set up to trigger parameterized build on Project3 with parameter

   SOURCE_JOB_NAME=$SOURCE_JOB_NAME



3. Project3 has one build command:

   echo Source project name is \"$SOURCE_JOB_NAME\"

Problem

When building Project1, Project3 prints the following as expected:

Source project name is "Project1"

But, when manually triggering Project2, then Project3 prints:

Source project name is "$SOURCE_JOB_NAME"

I would expect it to print:

Source project name is ""

Which is the normal behaviour when playing around with variables in sh.

---
Originally reported by mabahj, imported from: Non-existing parameters are not empty but replaced with parameter name

• status: Open
  
• priority: Major
  
• component(s): parameterized-trigger-plugin
  
• resolution: Unresolved
  
• votes: 2
  
• watchers: 2
  
• imported: 2025-12-07
  

Raw content of original issue

Version



	
Jenkins Parameterized Trigger plugin 2.11

	
Jenkins ver. 1.424



Setup



	
Project1 is set up to trigger parameterized build on Project2 with parameter



SOURCE_JOB_NAME=$JOB_NAME



	
Project2 is set up to trigger parameterized build on Project3 with parameter



SOURCE_JOB_NAME=$SOURCE_JOB_NAME



	
Project3 has one build command:



echo Source project name is \"$SOURCE_JOB_NAME\"





Problem

When building Project1, Project3 prints the following as expected:



Source project name is "Project1"



But, when manually triggering Project2, then Project3 prints:



Source project name is "$SOURCE_JOB_NAME"



I would expect it to print:



Source project name is ""



Which is the normal behaviour when playing around with variables in sh.