From customer,

I think it would be nice if the configuration necessary conditions where processed regardless of the build queue or had their own queue. Here is an example as to why this is useful:

1. I have set my build queue to 3 processes.
2. Let's say that all 3 processes are being used for builds that could take 30 minutes
3. All of the other continuous builds are in the queue waiting for 1 of these 3 to finish
4. However, what if most of the continuous builds waiting do not need to actually build because nothing has changed in the repo
5. They still sit there in the queue clogging it up waiting on 1 of these 3 to finish when they could quickly be processed to find out nothing has changed and removed from the queue
6. If the builds currently building take 1 hour or longer, then my queue could fill up really fast as each continuous build gets kicked off every 20 minutes. This means we have a situation where the queue grows faster than they can be processed.

Sure, I can change my continuous build timer to something longer than 20 minutes, but I thought that if the 95% of those builds don't actually have to be built because nothing has changed, then they should be processed right away without having to wait for the build queue to clear. So maybe have a separate queue just for processing the build necessary condition before putting them on the real build queue?