I'm not sure if it is something I have miss-configured or if I'm simply trying to use the tool in the wrong way, but when a new build of a project happens after a version changes, downstream builds are started based on the previous version of that module.
For example, I have two projects, moduleA and moduleB, both at version 1.0.0 and moduleB depends on moduleA. If updates are made to moduleA and the version changed to 1.0.1-SNAPSHOT, it will kick off a build of moduleB even though moduleA is now 1.0.1-SNAPSHOT and moduleB specifically depends on version 1.0.0, and looking at the list of upstream modules in moduleB will still list the job for moduleA. After a few minutes pass, moduleA will no longer be listed as an upstream project for moduleB, and builds of moduleA will no longer cause a build of moduleB. Is there a way to force an update of the downstream/upstream relationships when building a project so that the first build of moduleA after the version change doesn't build moduleB? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3379931c-2c57-4f90-a9ab-29abd183a149%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
