Ask HN: What is your monolith's CI build model?

For example, we're a team of ~80 developers and our model is that we have 1 Jenkins job per developer and 1 for the 'master' branch. Developers push to a corresponding git branch via a handy alias (`git testit`) and Jenkins triggers their corresponding build. So we have N+1 Jenkins jobs (where N=no. of devs). Then we have 3 executors, each waiting listening for all types of builds (master or dev builds).

I'd be interested in knowing how people are structuring their CI. Do you have a single job for your monolith's unit tests? Or do you also use multiple jobs (for specific branches or devs).