Hi, We have a set of projects A, B, C, D which are set in Jenkins and built on request. These are all Maven 2.x projects.
All the above mentioned project depend on a 'common' project from which certain jars are copied to them. Common project is also a maven project and starts with a clean install. The problem is that if multiple upstream projects are triggered at the same time then the common project goes into a clean-install loop and the jars to be copied are not available. For example: Project A is triggered - it triggers 'Common' - common completes and send the control back to 'A' for copying the jars In the meanwhile Project B is triggered - it triggers Common - maven starts with a clean-install and the Jars are removed Project 'A' fails since the jars to copy are no longer there. Is there a way to control the downstream project? I have looked at the 'Throttle Concurrent Builds' plugin but want to know if there is any other mechanism to control this? Thanks, Vikas -- 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. For more options, visit https://groups.google.com/d/optout.
