www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <herve.bout...@free.fr>
Subject Re: [IMPORTANT] - A lot of jenkins jobs have been changed!
Date Fri, 11 Nov 2016 03:52:17 GMT
Le jeudi 10 novembre 2016, 15:40:03 CET Robert Munteanu a écrit :
 (snip)
> 
> Thanks for taking care of the overall health of the Jenkins system,
> much appreciated.
+1

> 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.
this is something that I'm interested to do with Maven, but I'd need:

- some pointers on how to do it: I'm not a Jenkins expert, and I suppose I'm 
not the only one, then this could be useful for others too
found [1]: that looks a good start: thank you Robert :)
I don't know if this should be generalized, nor where to put information 
(MoinMoin Jenkins Wiki page, or new infra pages on Jenkins nodes...)

- some feedback if this really won't affect the Jenkins instance performance 
if every project does the same: the number of (little) jobs will grow a lot, 
to replace one big job that rebuild in 1 row a lot of independant parts. I see 
for example that Sling defined 2 views to separate "build view" (with many many 
jobs) from "dashboard  for builds that need attention" (with the few currently 
"interesting" ones)

Any objection for me to start doing the same on Maven Jenkins jobs?

Regards,

Hervé

> 
> Best,
> 
> Robert
> 
> [0]: https://builds.apache.org/view/S-Z/view/Sling/

[1] https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup

Mime
View raw message