Setting priorities is not making it work in correct order i think. Only on nightly build there will be a "priority" based order. But any build during the day is supposed to be FIFO. So logically I would want FIFO during nightly builds too and separate the que in time, creating the wanted order. For example: I set priorities A=1 B=2 C=3 D=3 in the above example. I might now get the correct buildorder during the nightly build. Then during continuous integration on daytime, Project gets triggered in this order through check-in: D, C, B, A. What happens then? 1. D is first cause it starts to build. 2. C is in que 3. B is now put first in que due to priorities 4. A is now first due to priorities followed by B and then C. 5. A builds 6. B builds 7. C builds. 8. Project owner of C and B are pissed of for having to wait for A eventhou they checked in first. Expected build order was D, C, B, A. Seams like it would be very easy to implement FIFO with priorites. Just asign a que number from the order something was put in que. Then draw the project from the que first based on priority and then based on the que number. This solves my problem but maintain priorities function. Regards MrK
On Tuesday, September 27, 2011 8:23:52 PM UTC+2, Ruben Willems wrote: > Hi > > what's the problem with setting priorities? > this should take care of the problem you have. > > if not, let is know, it definitely will be a hard one to simulate, let > alone fix. > > with kind regards > Ruben Willems >
