[JIRA] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work

Tue, 04 Feb 2014 10:13:21 -0800

Alex Earl commented on Bug JENKINS-20804

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.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to