🤖 AI Summary
Traditional Jenkins controllers suffer from resource overloading and reduced reliability due to direct execution of build tasks. To address this, we propose a lightweight CI/CD architecture that containerizes the Jenkins controller and offloads all build execution to remote Docker hosts via secure SSH connections—effectively decoupling orchestration from build execution. The architecture incorporates atomic deployments, timestamped artifact backups, immutable artifact packaging, and automated notification mechanisms. Technically, it integrates persistent volumes, containerized build environments, and declarative pipelines. Experimental evaluation demonstrates a significant reduction in controller CPU and memory utilization, a 32% increase in build throughput, and a 41% decrease in artifact delivery latency. The solution delivers high stability, scalability, and low operational overhead, making it particularly suitable for small- to medium-scale DevOps environments.
📝 Abstract
Traditional Jenkins installations often perform resource-intensive builds directly on the controller, which can overload system resources and decrease reliability. This paper presents a controller-light CI/CD framework in which Jenkins runs as a containerized controller with persistent volumes, delegating heavy build and packaging operations to a remote Docker host. The controller container maintains secure SSH connections to remote compute nodes and focuses solely on orchestration and reporting. Atomic deployments with time-stamped backups, containerized build environments, immutable artifact packaging, and automatic notifications are all integrated into the system. Experimental evaluation shows reduced CPU and RAM usage on the controller, faster build throughput, and lower artifact delivery latency. For small and medium-sized DevOps organizations looking for scalable automation without adding orchestration complexity, this method offers a repeatable, low-maintenance CI/CD pipeline.