Open dduportal opened 2 years ago
Issues that could have benefited from this:
Is there a reason to not move ci.jenkins.io to k8s?
Is there a reason to not move ci.jenkins.io to k8s?
When the AKS cluster was created (long time ago):
Both these historical reasons are gone since months if not years:
I don't see any reason not to move ci.jenkins.io to k8s honestly, only benefits:
There are 2 blocking points though:
Summary
Switch job configuration and management as code for ci.jenkins.io instead of manual management.
Why
There is no audit of which configuration changed was applied on the jobs on ci.jenkins.io. It's a concern for:
Also, managing jobs configuration as code would allow us to remove the "job config" plugin which is known to slow down instances.
What
⚠️ Using job-dsl introduces the following challenges to be aware of:
Reproductibility / maintanibility: the development lfiecycle is not easy and requires Jenkins expertise to really understand the domain.
helm template
should be good enough :) ) without requiring a migration to Kubernetes (that would be another topic for ci.jenkins.io).Job scanning / Scalability: given the huge amount of jobs (plugins...) , the time required for job-dsl to process scanning job configuration during a restart could be an issue. It's hard to evaluate to be fair.