Hi, I'm having trouble using the Multijob plugin... jobs become deadlocked. Let me explain...
Say I have a compilation job A which is triggered by a gerrit event (a code merge, for example); compilation is able to run in a farm of compilation servers. When compilation finishes, A proceeds with a multijob stage with a few parallel test jobs (B, C, D...), and A waits for those to be completed; test jobs run in parallel, using their own dedicated test servers. Now that works pretty well, except that it seems that every time a job A is triggered (manually or by gerrit) and put in the queue, it blocks *any* test jobs from executing, even if they were triggered by a different A. Instead of "waiting for next available executor" they show "Upstream Job XXX in build queue". This leads to the deadlocks that I mention. So in a very simplified example: A is compilation, B, C are tests; there's one server for compilation (S1), and one for test (S2). A1 is started, and starts to execute in S1; it finishes the compilation, it kicks off B1 and C1, and waits; B1 is scheduled and starts to run in S2, while C1 stays in the queue. Now another merge goes in so A2 is triggered, and put in the queue: it will jump to the front of the queue, and it will block C1 from being executed, even after B1 is done and S2 becomes available; so A1 will never finish, and A2 will never execute. Deadlock. I've tried to use the priority sorter plugin, but it doesn't help. A always trump any B and C. What am I missing? Is this a bug, or am I completely misunderstanding what the plugin provides? Thanks, -- Alvaro -- 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/groups/opt_out.
