Hi Geoff, I am afraid I cannot run concurrent downstream jobs since the downstream job clean up the workspace when starting.
What I would like to achieve is that the upstream joo can choose dynamically the downstream jobs. Let´s say we have downstream jobs A and B (actually they do the same thing but I need to keep them separated since the workspace is copied to the upstream job afterwards) I would like to be able to choose either A or B in the upstream job depending on the A and B job availability (i.e. if they are running or not) as I have described in the first post. Please let me know if you have any suggestions Thanks Alberto Il giorno mercoledì 9 ottobre 2013 08:40:23 UTC+2, Moral ha scritto: > > Hi Geoff, > > Thanks for the email. > > The downstream job is generating the c++ code from matlab models > (simulink). > > At the end of the downstream job the upstream job is copying all the > generated code with copy artifacts plug in (copy from the downstream > workspace to the upstream workspace). > > I would like to try to enable the concurrent builds for downstream to see > if we have some conflicts. > > Could you please point me out how to enable this feature in Jenkins? > > Thanks > > Alberto > > Il giorno martedì 8 ottobre 2013 15:13:23 UTC+2, Geoff Cummings ha scritto: >> >> Hi, >> >> Have you tried enabling concurrent builds of the downstream job so it can >> do more than one build at a time? >> >> You should check that the multiple builds of the same job don't interfere >> with each other... >> >> Geoff >> >> >> >> On 8 Oct 2013, at 12:13, Moral <[email protected]> wrote: >> >> Hi All, >> >> Our setup is: >> >> Tomcat 7.0.32 >> Jenkins 1.518 >> Multijob Plug in 1.9 >> >> We have multiple jobs that call a single downstream job for generating >> code from Matlab >> >> The upstream job takes the generated code from the downstream job and >> compile. >> >> The relationship between upstream and downstream jobs is M:1. >> >> In this setup if more then 1 upstream job is triggered only one can >> execute the downstream job and the others shall wait. >> >> I want to create more than 1 downstream job so the code generation can be >> run in parallel for multiple upstream jobs. >> >> To do that I need to be able to select dynamically at run time which >> downstream jobs can be executed by the upstream jobs. >> >> Something like (having two downstream jobs A and B) in each upstream job >> >> >> if downstream job A is not running then >> >> call the downstream job A >> >> >> else if downstream job B is not running then >> >> call the downstream job B >> >> >> else >> >> wait >> >> >> >> Our questions are: >> >> Is there a plug in or some strategy that can be used to achieved this? >> >> Is there a way to check if a downstream job is already executing? In this >> way I can use the test for implementing the logic described. >> >> Thanks >> ' >> Alberto >> >> >> >> -- >> 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 [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
