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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to