We have one Jenkins instance (master/slave setup) serving multiple versions of our product which we indicate by a suffix on the job name, e.g. 11a, LSV. However, for various internal reasons it is not indicated in ivy.xml for each module (i.e. identical organization, module and revision attributes) so we still need to match only on organization and module, i.e. we do not use the branch attribute. Currently, we are experiencing a somewhat strange behavior. With the following modules:

PC_CLI_11a
PC_CLI_LSV
PC_Persistence_11a
PC_Persistence_LSV

where CLI is dependent on Persistence, upstream/downstream modules are reported as:

PC_CLI_11a (Upstream: PC_Persistence_11a, Downstream: none)
PC_CLI_LSV (Upstream: PC_Persistence_11a, Downstream: none)
PC_Persistence_11a (Upstream: none, Downstream: PC_CLI_11a, PC_CLI_LSV)
PC_Persistence_LSV (Upstream: none, Downstream: none)

One way of solving this would be to bring in the job name into equation, e.g. a regular expression that must match in order to qualify as upstream/downstream dependency. Comments?

I have not yet looked at the code but will do soon so any pointers are welcome.