Thanks for checking.

This is what it does for showDependencies, I'm not real familiar with this code, so I can't comment on what exactly it should do

for (Entry<AbstractProject, DependencyChange> e : build.getDependencyChanges(previousBuild).entrySet()) {
    buf.append("\n=======================\n");
    buf.append("\nChanges in ").append(e.getKey().getName())
        .append(":\n");
    for (AbstractBuild<?, ?> b : e.getValue().getBuilds()) {
        for (ChangeLogSet.Entry entry : b.getChangeSet()) {
            Util.printf(buf, format, new ChangesSincePrintfSpec(entry, pathFormat, dateFormatter));
        }
    }
}

I am running into a similar issue with

Jenkins: 1.548
email-ext: 2.37.2

However, for me the email-ext plugin will return changes with dependencies IF the build ends with a FAILURE. If the build is unstable the changes will not be populated. Here are the settings I am using:

${CHANGES, showDependencies=true, format="[%a] %d, %r: %m
n %p
n"}

showDependencies uses the following code:

for (Entry<AbstractProject, DependencyChange> e : build.getDependencyChanges(previousBuild).entrySet()) {
    buf.append("\n=======================\n");
    buf.append("\nChanges in ").append(e.getKey().getName()).append(":\n");
    for (AbstractBuild<?, ?> b : e.getValue().getBuilds()) {
        for (ChangeLogSet.Entry entry : b.getChangeSet()) {
            Util.printf(buf, format, new ChangesSincePrintfSpec(entry, pathFormat, dateFormatter));
        }
    }
}

AbstractBuild.getDependencyChanges returns an EMPTY Map if there is no Fingerprinter.FingerprintAction for the project. The showDependencies is all based on core Jenkins classes, so you'd need to determine if your projects are meeting the requirements for the dependency graph being populated.

Thanks for your comment, Alex. I checked the dependency graph and it is populated correctly. However, in the job that has the test failures I am copying test artifacts around. Not sure if that is the problem, I enabled fingerprinting of the copied artifacts to no avail. The fact that the dependent changes are shown correctly IF the job does not complete (no tests run) but does not show dependent changes IF the job completes unstable (tests are run with some failing) indicates that the root cause could be the copying of files. I will try to investigate further and see if I can get it working.

Ok, I was able to resolve the issue by creating a correct chain of fingerprinting across my builds. The piece that was missing was that the build where I was not able to see dependent changes did not have a copy of the artifacts in the workspace. Although that particular build does not require the artifacts Jenkins needs them in the workspace to establish the connection that the build is dependent on a previous build that created the artifact. Since Jenkins does not support fingerprinting outside the workspace directory it is easiest just to use the "Copy artifacts from another build" option and tick the fingerprinting option.

I think we can close this issue then, anyone opposed?

Cool with me.

Please read Dirk's comments on how he got showDependencies=true to work.

Ok, I'll try it out.