Hi Gavin, On Thu, 2016-11-10 at 20:22 +1100, Gavin McDonald wrote: > Hi All, > > Yesterday whilst adding some new modes and re-configuring jobs & > nodes for removal of some Labels - as notified some weeks ago, I > noticed some > unusual configurations that could affect the overall performance of > Jenkins and affect everybody in general. > > The changes were wide spread and out of over 2000 builds I would say > at least 1500 of them are affected in one way or another. > To point out, none of this is drastic, and your builds are not > affected in terms of software configurations. But a hammer was used > here to > change a lot of builds at once, to make them more uniform. > > A few things were changed.
(snip) Thanks for taking care of the overall health of the Jenkins system, much appreciated. In the Apache Sling project we're managing a sizeable number of jobs ( 530 at the moment ) [0] using the Job DSL Plugin to make it feasible to look after such a large number of jobs. The jobs are quite small, usually don't archive artifacts ( we deploy to repository.apache.org ) and many of them are triggered rarely, so they should not have a negative impact on the health of the Jenkins server. I rather suspect we have reduced our load since we rebuild a much smaller part of the project whenever anything changes. I want to point out 2 things: 1) If you think that we're doing something wrong in the project configs do let us know separately - the manual changes you might apply will be overwritten without us noticing. 2) I would encourage more projects to manage their Jenkins configurations in version control, either by using a Jenkinsfile or the Job DSL plugin, it makes it much simpler to maintain your configuration in time and easier to collaborate on. Best, Robert [0]: https://builds.apache.org/view/S-Z/view/Sling/
