A customer of mine reported a weird behavior using maven snapshot dependencies to trigger builds
as a resume, he has maven jobs A, B, C B depends on A-SNAPSHOT C depends on A-SNAPSHOT and B-SNAPSHOT A is an active project, so is more or less always building same for B as a direct dependent job then C is only built once a day when all other builds complete after developer have left. This is due to https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/AbstractMavenProject.java#L76 if (areUpstreamsBuilding(downstreamProject, parent)) { maven-plugin explicitly prevent downstream job to get trigger because some upstream modules are currently building. I guess this has been introduced for more complex scenarios where some upstream get build quickly vs other longer ones and need to wait for a stable state, As a better implementation (?) would it make sense to check upstream currently nuilding have been triggered by the same cause ? So commit #1 to A will trigger A #1, then B #1 If in the meantime commit #2 trigger A #2, on B#1 completion the upstream building A would not match the criteria and C would get triggered. wdyt ? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
