I would like this as well. We use a lot of MultiJob jobs, but the build failures analysis doesn't appear to aggregate on the MultiJob job.

There is also the Parameterized Trigger Plugin that allows to trigger other jobs.
If such a build step is configured to let the job fail if the result of the triggered job has a certain status, it would be nice to automatically populate the indications from those builds.

As soon as I understand, this is not possible to do manually by using the existing features.

Is there any chance this is going to be an option?
Can I contribute to make it happen?

Best Christian

The parameterized trigger plugin is already supported.

If you set the build to wait for the sub-build to finish, the found failure causes from the sub build
will be propagated up to the calling build.

The MultiJob isn't supported yet and is nothing I have planned to implement. I would gladly accept pull requests for the functionality though.

Well, very interesting because I'm using it on one installation for abut a week now and couldn't see that happen.
Since which version is this supported?
Is some kind of setting/ configuration combination required for this to work?
E.g. does this only happen if no case was found in the "parent" job?
How to track what goes wrong if this is not working as you describe?
(I'm going to set up a minimal example to verify that, so it would be helpful to know where to look.)

Thx
Christian

Propagating downstream builds to the upstream build have been in the plugin since 1.21, which was released January 2015.
The only configuration needed is:

Create job a which triggers job b as a build step and waits for it to finish.
Have job b fail.

The failure causes found on b should appear on the build page for a.

Are you triggering job b from a build step or a post-build step? If you do it from a post build step or you choose to not wait for it,
then the functionality doesn't work, since job a is long since done running when project b is finished.

Just installed the plugin some days ago, the version is 1.16.0.
The Parameterized Trigger Plugin is installed with version 2.30
From the changelog, I assume you mean that you are referring to version 1.12.1 that added it.
Our Jenkins has the version 1.658 (currently latest on the 1.x branch).
Just check a build chain four levels deep, all of them trigger it as a build step and wait for the result.
Is there a chance the plugin only looks for causes in triggered jobs if they did not find something in their own log?
(I wrote an indication to display which child job caused the build to fail, maybe this blocks the traversal?)

Best
Christian
PS: Should we have a separate ticket for this?

Yeah, maybe you should open a separate ticket for this, this discussion has nothing to do with the MultiJob plugin.
Yes, I mean 1.12.1.

Just to make sure, can you test out the very basics of the functionality and add on more complexity as you go along?

If you create a job with one build step, a "trigger/call builds on another project", and in the other
job, create one build step that fails, what is your result in BFA? No text saying "Subproject build" and a link to the failure
in the subproject build? This is very basic functionality that I can reproduce in a minute or so, so I'm very curious what is going
wrong at your end.

Ok, I will build the most simple scenario as soon as I can find time for it, and file a new ticket for that afterwards.
Thx so far