Yup, we do the same. We made sure that jenkins doesn't fiddle with the environment, so that everything was derived from the various networked user accounts. u

Yup, we do the same. We made sure that jenkins doesn't fiddle with the environment, so that everything was derived from the various networked user accounts. using @hourly, it spreads the load evenly over the hour to even out resource starvation spikes. We have jenkin's job builder(and yaml) in a git repo to make sure that the delicate snowflake that is jenkins is repeatable.