I'm guessing that you are talking about functional test. in this case what we normally do is putting them into groups or sections like UI or model, or what ever gives sense in you project and then you can fron the job have an overview of that part of the code.
2013/8/28 Zhanglei Wang <filam...@gmail.com> > I'm using Jenkins to launch thousands of test jobs. Each test may take > several minutes to finish and is likely to fail. So I want to launch one > build job for each test, instead of aggregating them using scripts. > > I wonder if this is a bad practice? Is there a length limit on the build > queue? Will it cause performance issues? > > One obvious inconvenience is that the web UI becomes irresponsive. The > build queue section in the left side bar is too long and takes a long time > to refresh, making the UX very bad. Is there anyway to limit the number of > items to display? > > Thanks. > > -- > 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. > -- [image: ____________________________________________________________]<http://www.praqma.net/> *Jes Struck, * Consultant j...@praqma.net +45 31 42 09 00 Skype:jes.struck *Praqma A/S* www.praqma.net Allerød Stationsvej 4 DK-3450 Allerød +45 36 77 27 62 <http://www.praqma.net/jciusrcph12><http://www.praqma.net/jcicodecamp12> -- 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.
