[JIRA] (JENKINS-62165) Space character at end of parameter name prevents dereferencing this parameter

2020-05-06 Thread sesa53...@se.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Firmware Tools SE reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Okay, it seems I was misunderstood. Adding a space after the parameter name on purpose was just for the sake of the example. I spent quite some time figuring out some user had indeed mistakenly added a space behind a parameter name (probably a wrong copy/paste) in a weekly multijob (leading to failure of some parts of it). So my request is: could it be possible to add some control on whether a parameter name has trailing (or even leading) "invisible" characters (maybe a warning or an automatic trimming (who, in his right mind, would want a trailing space in a parameter name?)).    
 

  
 
 
 
 

 
 Jenkins /  JENKINS-62165  
 
 
  Space character at end of parameter name prevents dereferencing this parameter   
 

  
 
 
 
 

 
Change By: 
 Firmware Tools SE  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-62165) Space character at end of parameter name prevents dereferencing this parameter

2020-05-05 Thread sesa53...@se.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Firmware Tools SE created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-62165  
 
 
  Space character at end of parameter name prevents dereferencing this parameter   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2020-05-05 15:03  
 
 
Environment: 
 Jenkins LTS 2.222.3  Linux CentOS 7   
 
 
Priority: 
  Major  
 
 
Reporter: 
 Firmware Tools SE  
 

  
 
 
 
 

 
 When a space character is present at end of a parameter name, dereferencing this parameter name (without space) will display the string attemting the dereference (i.e. ${name}) instead of the value of this parameter.   Example of this problem: 
 
Create a job with a string parameter (e.g. "top_parameter"), but add a space at the end of the name like "top_parameter ", with a default value of anything (e.g. 42) 
use the parameter value, for example in a build step "Inject Environment variables" like : top_value=${top_parameter} 
use "top_value" environment variable (e.g. in a shell) ; its value will be the string "${top_parameter}" not 42