|Re: [cross-project-issues-dev] Avoid blocking builds on Hudson|
hi Eike, comments below : Eike Stepper a écrit :
Hi everybody,I noticed that some Hudson jobs tend to stay in the queue forever because something in their execution is blocking. Thereby taking away slots that could be used by pending jobs.
yes, especially when both galileo and helios epp jobs are running :)
I think it's a good idea to set an adequate timeout value in the Hudson job config. The property is called something like "Abort blocking builds".
the exact property on the job's config page is " Abort the build if it's stuck " and you can set a timeout (minutes based).
Tests should generally be designed such that they can not block indefinitely. For example, use (short) timeouts in statements like CountDownLatch.await() or similar.BTW. I find it rather hard to determine a build's contact email. Is there a trick that I don't know of?
Don't know either, but good practice should be to always have a contact in the config's page ( in the notification property) so that people that can access to it can use that contact.
Cheers /Eike ---- http://thegordian.blogspot.com http://twitter.com/eikestepper _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
begin:vcard fn;quoted-printable:St=C3=A9phane Bouchet n;quoted-printable:Bouchet;St=C3=A9phane org:Obeo adr;quoted-printable:BP 20773;;7 Boulevard Amp=C3=A8re;CARQUEFOU;;44481;France email;internet:stephane.bouchet@xxxxxxx tel;work:02-51-13-61-67 x-mozilla-html:FALSE url:http://www.obeo.fr version:2.1 end:vcard
Back to the top