jenkinsci / jenkinsci/parameterized-trigger-plugin

[JENKINS-50934] Triggered builds "for every property file" do not receive the parameters from the property files

Open
#746 1 comment 0 reactions 0 assignees View on GitHub
component:parameterized-trigger-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
77
Forks
174
Avg merge
22h 27m
Merged PRs (30d)
1

Description

I set up job A which has a single Trigger/call builds on other projects build step which can be seen in the attached screenshot. It's set For every property file, invoke one build of job B. The File Pattern is /var/lib/jenkins/cases/*

 

Job B ("case-runner" in the screenshot) is parameterized, it has a DATASET parameter and a single build step Execute shell "env". It is started as expected, but the DATASET parameter is not passed through even though it's specified in the property file.

 

 

jenkins@​instance-eval-jenkins:~$ ls -l /var/lib/jenkins/cases/

total 4

rw-rr- 1 jenkins jenkins 12 Apr 19 13:08 a

jenkins@​instance-eval-jenkins:~$ cat /var/lib/jenkins/cases/a

DATASET=svo

 

The DATASET parameter should be passed through according to the documentation: "This ParameterFactory generates parameters based on the contents of the files found."

 

DATASET is passed fine if I specify it in a list of Predefined parameters, but not when it's in the property file, so it seems to be a problem with how the job is triggered. Both jobs run on the master Jenkins node. I also tried with "DATASET = svo" in the property file but still the same.

 

---
Originally reported by aleb, imported from: Triggered builds "for every property file" do not receive the parameters from the property files


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

Raw content of original issue

I set up job A which has a single Trigger/call builds on other projects build step which can be seen in the attached screenshot. It's set For every property file, invoke one build of job B. The File Pattern is /var/lib/jenkins/cases/*
 
Job B ("case-runner" in the screenshot) is parameterized, it has a DATASET parameter and a single build step Execute shell "env". It is started as expected, but the DATASET parameter is not passed through even though it's specified in the property file.
 
 
jenkins@instance-eval-jenkins:~$ ls -l /var/lib/jenkins/cases/
total 4
rw-rr- 1 jenkins jenkins 12 Apr 19 13:08 a
jenkins@instance-eval-jenkins:~$ cat /var/lib/jenkins/cases/a
DATASET=svo
 
The DATASET parameter should be passed through according to the documentation: "This ParameterFactory generates parameters based on the contents of the files found."
 
DATASET is passed fine if I specify it in a list of Predefined parameters, but not when it's in the property file, so it seems to be a problem with how the job is triggered. Both jobs run on the master Jenkins node. I also tried with "DATASET = svo" in the property file but still the same.
 

environment

```
Jenkins ver. 2.107.1

Parameterized Trigger plugin 2.35.2
```

1 attachment

- [Screen Shot 2018-04-19 at 15.35.35.png](https://issues.jenkins.io/secure/attachment/42247/Screen%20Shot%202018-04-19%20at%2015.35.35.png)
> ![Screen Shot 2018-04-19 at 15.35.35.png](https://issues.jenkins.io/secure/attachment/42247/Screen%20Shot%202018-04-19%20at%2015.35.35.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.