[JENKINS-64591] Multi-configuration project ALWAYS triggers parametrized build for ALL childs if a pipeline job in the project list to build

Let's compare behavior of  a pipeline job and a freestyle job when they are triggered as parametrized build in the Post-Build section from a Mutli-configuration job.

In my example I have a multi-configuration job :

test-parametrizedPlugin-multi-conf-job that calls 2 jobs one freestyle and one pipeline :

• test-parametrizedPlugin-called-pipeline-job


• test-parametrizedPlugin-called-freestyle-job

 

First test, the 2 jobs are in the same Projects to build list( Note that the Trigger build from child project option is not set ):

Then the 2 jobs are triggered for each child as we can see as it is reported in the console logs of the 2 called jobs.

Second test, the 2 jobs are in separate Projects to build list( Note that the Trigger build from child project option is not set ) :

Then the 2 jobs are triggered but not with the same behavior,

freestyle job is run as expected :

but pipeline job is run for each child as we can see as it is reported in the console log:

---
Originally reported by merlindam, imported from: Multi-configuration project ALWAYS triggers parametrized build for ALL childs if a pipeline job in the project list to build

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

Raw content of original issue

Let's compare behavior of  a pipeline job and a freestyle job when they are triggered as parametrized build in the Post-Build section from a Mutli-configuration job.


In my example I have a multi-configuration job :


test-parametrizedPlugin-multi-conf-job that calls 2 jobs one freestyle and one pipeline :



	
test-parametrizedPlugin-called-pipeline-job

	
test-parametrizedPlugin-called-freestyle-job



 


First test, the 2 jobs are in the same Projects to build list( Note that the Trigger build from child project option is not set ):




Then the 2 jobs are triggered for each child as we can see as it is reported in the console logs of the 2 called jobs.






Second test, the 2 jobs are in separate Projects to build list( Note that the Trigger build from child project option is not set ) :




Then the 2 jobs are triggered but not with the same behavior,


freestyle job is run as expected :




but pipeline job is run for each child as we can see as it is reported in the console log:

environment

```
Jenkins Version: 2.263.1

Parametrized trigger Plugin Version : 2.39
```

10 attachments

- [image-2021-01-11-09-16-00-517.png](https://issues.jenkins.io/secure/attachment/53798/image-2021-01-11-09-16-00-517.png)
> 
- [image-2021-01-11-09-16-21-386.png](https://issues.jenkins.io/secure/attachment/53797/image-2021-01-11-09-16-21-386.png)
> 
- [image-2021-01-11-09-29-16-578.png](https://issues.jenkins.io/secure/attachment/53796/image-2021-01-11-09-29-16-578.png)
> 
- [image-2021-01-11-12-16-43-482.png](https://issues.jenkins.io/secure/attachment/53795/image-2021-01-11-12-16-43-482.png)
> 
- [image-2021-01-11-12-18-12-082.png](https://issues.jenkins.io/secure/attachment/53794/image-2021-01-11-12-18-12-082.png)
> 
- [image-2021-01-11-12-25-08-737.png](https://issues.jenkins.io/secure/attachment/53793/image-2021-01-11-12-25-08-737.png)
> 
- [image-2021-01-11-12-28-05-382.png](https://issues.jenkins.io/secure/attachment/53792/image-2021-01-11-12-28-05-382.png)
> 
- [image-2021-01-11-12-30-19-317.png](https://issues.jenkins.io/secure/attachment/53791/image-2021-01-11-12-30-19-317.png)
> 
- [jobs_config_parametrizedPluginIssue_3.zip](https://issues.jenkins.io/secure/attachment/53801/jobs_config_parametrizedPluginIssue_3.zip)
- [jobs_config_parametrizedPluginIssue_4.zip](https://issues.jenkins.io/secure/attachment/53802/jobs_config_parametrizedPluginIssue_4.zip)