Similar issue to JENKINS-7535, but in the Ivy Plugin instead of the Maven Plugin.

Every time a project is saved, Jenkins rebuilds the dependency graph.
For Ivy Projects this includes building up a dependency map of all the Ivy modules in Jenkins and then applying the build triggers based on that information. Currently, this is being done in every single module resulting in an operation which is roughly in the order of O(n^2 + xn) where n is the number of Ivy modules in Jenkins and x is the average number of direct dependencies each module has.