If I've understood your description correctly, this has nothing to do with the downstream-ext plugin, but only with the parametrized trigger!?

I do not know, who is responsible or which plugin is causing this effect, that is why I chose both plugins as affected components. (Then JIRA automatically assigned the issue to you, Christoph [kutzi].)

I wanted to show that it obviously is the combination of both plugins not producing the expected output.

So Christoph: If you have the opinion that it's the "Parameterized Trigger plugin" which causes this, please feel free to change the assignee to Tom [huybrechts].

Assigning to parameterized-trigger component only.
And BTW my name is Christoph, that's at least what my ID card said the last time I checked it.

And BTW my name is Christoph, that's at least what my ID card said the last time I checked it.

SORRY! - I was doing too many things in parallel and mixed-up your name! (I corrected the above comment accordingly.)

My understanding of JENKINS-5184 is that parameterized-trigger now contributes to the core dependency graph. If that's true, then perhaps downstream-ext isn't looking at the right datastructures to generate the report.

mdonohue: if I understand the problem report right, the user isn't even using the downstream-ext trigger for this job.
BTW: What report are you talking about? Downstream-ext doesn't create any reports.

ilenseer: have you checked the 'Build other projects (extended)' section in your build config? If not, you're not using downstream-ext for this job.

Apologies. It is the Downstream buildview plugin that is being used here, I thought that screen was coming from downstream-ext, but it is not - there is no component for downstream-buildview right now.

[sorry was on a business trip with limited internet access..]

Yes, my apologies! - It is the "Downstream build view" plugin I am referring to.
This plugin should list all child projects, but obviously does not.

Attached patch fixes the problem by using DependencyGraph.

Applied patch, downstream build view works as expected! A minor thing is that the icon to the left of each package name/link is not displayed, just a placeholder, but that's OK for my purposes.

Will this patch be contained in an updated build of the downstream-buildview component, so that it is available by download/upgrade in the Hudson plugin manager interface and when?

Hello,

I've been trying to use the patch but I'm not able. I'm not sure if I'm following the right steps to fix the problem. This is what I've done:

1. download the code of the pluging "Downstream-buildview"
2. apply the diff file
3. Use maven commands "mvn package" and "mvn install" to create a *.hpi file.

There is when I get the errors... it says that files javanettasks-1.0.12.pom, commons-jexl-1.1-hudson-20061106.pom, commons-jelly-1.1-hudson-20070821.pom and groovy-all-1.0-jsr-06.pom are invalid and then I got a build error.
Any idea? Will be a new version of the plugin available to update?

Thanks!

I've created a pull request with the patch (which I can also say works fine).

https://github.com/jenkinsci/downstream-buildview-plugin/pull/1

It would be great if someone could pull it in...

Code changed in jenkins
User: David Resnick
Path:
src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewAction.java
http://jenkins-ci.org/commit/downstream-buildview-plugin/ccc4d3c11cd3174f41f077c43d88254e257083da
Log:
Fix for 'Projects triggered by "Parameterized Build Plugin" do not show in view with "Downstream-buildview"' (https://issues.jenkins-ci.org/browse/JENKINS-5761)

Applied patch created by samodelkin (https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=samodelkin) and attached to the JENKINS-5761.

Code changed in jenkins
User: David Resnick
Path:
src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewAction.java
http://jenkins-ci.org/commit/downstream-buildview-plugin/bc058cac4f10f60c97f3e45cd826d865a1ecdd2e
Log:
Fix for JENKINS-5761 ('Projects triggered by "Parameterized Build Plugin" do not show in view with "Downstream-buildview"' - https://issues.jenkins-ci.org/browse/JENKINS-5761)

Applied patch created and attached to JENKINS-5761 by samodelkin.

Code changed in jenkins
User: David Resnick
Path:
src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewAction.java
http://jenkins-ci.org/commit/downstream-buildview-plugin/1ed963cb4e8d34a7644fe9d288eef63fea698a66
Log:
Merge branch 'JENKINS-5761' of https://github.com/david-resnick/downstream-buildview-plugin into JENKINS-5761

Code changed in jenkins
User: David Resnick
Path:
src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewAction.java
http://jenkins-ci.org/commit/downstream-buildview-plugin/471be17f7581ac04ac2fbddefbaebb6ad8162fd8
Log:
Fix for 'Projects triggered by "Parameterized Build Plugin" do not show in view with "Downstream-buildview"' (https://issues.jenkins-ci.org/browse/JENKINS-5761)

Applied patch created by samodelkin (https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=samodelkin) and attached to the JENKINS-5761.

Code changed in jenkins
User: David Resnick
Path:
http://jenkins-ci.org/commit/downstream-buildview-plugin/8a3f323a8a73df7873ecab50308ae050e7093066
Log:
Merge branch 'JENKINS-5761' of https://github.com/david-resnick/downstream-buildview-plugin into JENKINS-5761

Code changed in jenkins
User: Olivier Lamy
Path:
src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewAction.java
http://jenkins-ci.org/commit/downstream-buildview-plugin/12442372e2d7d23f6126216bbdf64a7e203a9063
Log:
Merge pull request #1 from david-resnick/JENKINS-5761

[FIXED JENKINS-5761]

Compare: https://github.com/jenkinsci/downstream-buildview-plugin/compare/c0ce12c...1244237

I still encountering this problem with Jenkins 1.510 and Downstream build view 1.8 and Parametrized Trigger 2.18

same here.