Is there an easy way to clear what jenkins thinks the up/downstream jobs are for any given job?
We have an issue where we cut a branch but it appears not all poms were updated fast enough so that foo and foo-1.0 are both downstream of bar-1.0. This seems to kick off foo and foo-1.0 builds when bar-1.0 runs. Additionally, another scenario where a dependency was severed is still listing that dependency as an upstream job (and in this case, resulting in a whacky circular build loop). Halp!
