[JENKINS-34340] Don't rename job names in TRIGGERED_JOB_NAMES

I'm using parameterized-trigger-plugin like this :

• job A runs on master , triggers job trigA on slave


• trigA once finised publishes some output back to master


• then job A goes on ...and tries to find the files published by trigA

TRIGGERED_JOB_NAMES could be helpful, but why the hell replace characters from original names ? By doing so, it's impossible to use these names to build the path to trhe triggered jobs workspace.

If you want to stick to this behaviour, would it be possible to have variables set to triggered_jobs_master_workspace for instance ?

---
Originally reported by squalou, imported from: Don't rename job names in TRIGGERED_JOB_NAMES

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

Raw content of original issue

I'm using parameterized-trigger-plugin like this :



	
job A runs on master , triggers job trigA on slave

	
trigA once finised publishes some output back to master

	
then job A goes on ...and tries to find the files published by trigA



TRIGGERED_JOB_NAMES could be helpful, but why the hell replace characters from original names ? By doing so, it's impossible to use these names to build the path to trhe triggered jobs workspace.


If you want to stick to this behaviour, would it be possible to have variables set to triggered_jobs_master_workspace for instance ?

environment

```
jenkins LTS 1.651.1, parameterized-trigger-plugin 2.30

master on redhat 6.4 server, slaves on redhat 7.2
```

1 attachment

- [screenshot-1.png](https://issues.jenkins.io/secure/attachment/41823/screenshot-1.png)
>