Andrew: I know Jenkins tracks how big the queue is, is that something that we can graph over time? It'd be interesting to know how that's changed and will change, otherwise we'll constantly be fighting fires here.
I'd like to have the following items graphed: # of dynamic slaves in operation # of executors currently in use # of jobs in the queue # of jobs in the queue actually waiting on an executor. It'd be nice to know the average time waiting on an executor as well. I don't suppose Jenkins has any functionality that would allow us to run a quota per-project is there? Since you're one of the resident Jenkins experts how many additional build nodes/executors will satiate our current demand for capacity? --David On Tue, Aug 18, 2015 at 11:16 AM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Hey all - > > So as you may have noticed, we've seen an increase in build utilization on > builds.a.o in the last few months - which is great! The problem is that > we're seeing more demand than we have resources at this point, and that's > only going to increase. We're working on getting more slaves lined up, but > don't yet have a timeframe for that - we'll let you all know when we have > more news. > > A.
