Central CI/CD Service Provisioning

Project Challenge

• The existing infrastructure consisting of several "snowflake" Jenkins Masters and Nexus Repositories has evolved to an unmanageable degree. 
• Provide support for Java, JavaScript, C++, C#, Python. 
• Establish and enforce best practices across technologies as well as per technology. 
• Define and enforce baselines for code quality and code security.

Solution Provided

• Design of a scalable architecture for the central CI/CD service . 
• The CI/CD service consists of a multitude of tools: CloudBees Jenkins Enterprise, SonarQube, Sonatype Nexus Repository, Sonatype Lifecycle as well as Prometheus, Elasticsearch and Grafana for auditing and monitoring. 
• 4 Jenkins Masters and ~ 50 Jenkins agents on Linux, Solaris and Windows in a shared pool for ~300 developers. 
• Updates and upgrades incrementally every 3 weeks through Ansible.
• Connected services consist of Mercurial / Kallithea, Active Directory and a customer-specific deployment tool.

CI/CD infrastructure overview with central management layer, controlling Jenkins masters per project and OS-specific build agents.

© ASERVO Software GmbH