That is the standard Jenkins behaviour. You'll notice the same without the build-flow plugin.
On Friday, 15 November 2013 17:12:59 UTC, Zofia Majenka wrote: > > Hi, > > We are using the Build Flow Plugin in Jenkins. This is scenario: > > Start the flow 1: Job1 -> Job2 -> Job3 .... > > Start the flow 2: Job1 -> Job2 -> Job3 .... > > Start the flow 3: Job1 -> Job2 -> Job3 .... > > The same flow is started 3 times with a few minutes delay between them. > > We have noticed that thought the Job2 in the flow 3 is finished, it hangs > on upstream notification and the Job3 within the same flow 3 could not be > started. It waits until the Job2 in flow1 is finished and Job2 in flow2 is > finished. > Is it how it always works? The same job started in parallel (several > execution of the same test flow on different resources) tends to become a > serial? > > > Start Job2 flow1 > Start Job2 flow2 > Start Job2 flow3 > > Finish Job2 flow1 > Finish Job2 flow2 > Finish Job2 flow3 > > Is it possible to start as above but finish like this: > > Finish Job2 flow3 and start Job3 > Finish Job2 flow2 and start Job3 > Finish Job2 flow1 and start Job3 > > > Or there is something in configuration we are missing? The job is > configured to be executed in parallel. > > Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 > takes long time to execute? > > Regards > /Zofia > > -- 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.
