jenkinsci / jenkinsci/parameterized-trigger-plugin

[JENKINS-64576] Missing information reported in status page when triggered parametrized build ( Build Section) is a pipeline job

Open
#786 0 comments 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

Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

In my example I have a freestyle job :

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



  • test-parametrizedPlugin-called-pipeline-job

  • test-parametrizedPlugin-called-freestyle-job

In the status page of the job we see that the Subprojects part is OK but not the Downstream Projects part, the pipeline job is missing

And if we look in the status page of the run we see that the Subprojects part for the pipeline job is missing

Note that the 2 jobs were correctly started as we can see in the console log

---
Originally reported by merlindam, imported from: Missing information reported in status page when triggered parametrized build ( Build Section) is a pipeline job


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

Raw content of original issue

Let's compare how are reported a pipeline job and a freestyle job when they are triggered as parametrized build in the build section.

In my example I have a freestyle job :

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



  • test-parametrizedPlugin-called-pipeline-job

  • test-parametrizedPlugin-called-freestyle-job

In the status page of the job we see that the Subprojects part is OK but not the Downstream Projects part, the pipeline job is missing

And if we look in the status page of the run we see that the Subprojects part for the pipeline job is missing

Note that the 2 jobs were correctly started as we can see in the console log

environment

```
Jenkins Version: 2.263.1

Parametrized trigger Plugin Version : 2.39
```

7 attachments

- [image-2021-01-08-17-36-24-862.png](https://issues.jenkins.io/secure/attachment/53773/image-2021-01-08-17-36-24-862.png)
> ![image-2021-01-08-17-36-24-862.png](https://issues.jenkins.io/secure/attachment/53773/image-2021-01-08-17-36-24-862.png)
- [image-2021-01-08-17-37-12-357.png](https://issues.jenkins.io/secure/attachment/53772/image-2021-01-08-17-37-12-357.png)
> ![image-2021-01-08-17-37-12-357.png](https://issues.jenkins.io/secure/attachment/53772/image-2021-01-08-17-37-12-357.png)
- [image-2021-01-08-17-44-05-561.png](https://issues.jenkins.io/secure/attachment/53771/image-2021-01-08-17-44-05-561.png)
> ![image-2021-01-08-17-44-05-561.png](https://issues.jenkins.io/secure/attachment/53771/image-2021-01-08-17-44-05-561.png)
- [image-2021-01-08-17-49-39-541.png](https://issues.jenkins.io/secure/attachment/53770/image-2021-01-08-17-49-39-541.png)
> ![image-2021-01-08-17-49-39-541.png](https://issues.jenkins.io/secure/attachment/53770/image-2021-01-08-17-49-39-541.png)
- [image-2021-01-08-17-59-57-586.png](https://issues.jenkins.io/secure/attachment/53774/image-2021-01-08-17-59-57-586.png)
> ![image-2021-01-08-17-59-57-586.png](https://issues.jenkins.io/secure/attachment/53774/image-2021-01-08-17-59-57-586.png)
- [image-2021-01-08-18-01-33-502.png](https://issues.jenkins.io/secure/attachment/53775/image-2021-01-08-18-01-33-502.png)
> ![image-2021-01-08-18-01-33-502.png](https://issues.jenkins.io/secure/attachment/53775/image-2021-01-08-18-01-33-502.png)
- [jobs_config_parametrizedPluginIssue_1.zip](https://issues.jenkins.io/secure/attachment/53769/jobs_config_parametrizedPluginIssue_1.zip)

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.