-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
jenkins LTS 1.651.1, parameterized-trigger-plugin 2.30
master on redhat 6.4 server, slaves on redhat 7.2
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 ?
- relates to
-
JENKINS-14545 Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
-
- Resolved
-
I would have worded this differently, but I, too, stumbled across this problem. We trigger a parameterized job called "param-builder" and the environment variable turns this into:
essentially replacing all "-" with "_". While I can work around that it's still quite annoying to do so.
Also, having a variable with a link to the parameterized build would be nice.