Architecting Secure and Sustainable Enterprise Java Delivery Pipelines: Managing Mixed Java Versions, Legacy Modularity, and DevSecOps Automation in Non-Containerized CI/CD Environments

Abstract

Enterprise Java ecosystems continue to operate under complex constraints shaped by long-lived legacy systems, mixed Java version dependencies, stringent regulatory requirements, and cautious adoption of containerization technologies. While cloud-native and container-based paradigms dominate contemporary discourse, a substantial proportion of mission-critical enterprise systems still rely on non-containerized continuous integration and continuous delivery (CI/CD) pipelines. These environments face unique challenges, particularly when managing multiple Java versions, modularization transitions, dependency risk propagation, and integrated security controls without disrupting operational stability. This research presents an in-depth, theory-driven examination of enterprise-grade CI/CD pipeline architectures for mixed Java version environments using Jenkins in non-containerized contexts. Drawing exclusively from established academic, industry, and standards-based references, the study synthesizes insights from Java platform evolution, modularity research, garbage collection optimization, dependency management, and DevSecOps governance frameworks. The methodology employs a qualitative analytical approach, integrating comparative literature analysis, architectural reasoning, and process-oriented interpretation to derive best-practice patterns. The findings reveal that sustainable pipeline design in non-containerized environments depends on deliberate version isolation strategies, disciplined dependency governance, modular refactoring aligned with Java Platform Module System principles, and deeply embedded security automation. The discussion critically evaluates trade-offs between modernization and operational risk, highlighting how policy-as-code, static and dynamic analysis tools, and compliance-driven observability can be harmonized within Jenkins-centric pipelines. The study concludes that non-containerized CI/CD architectures, when systematically engineered, remain viable and strategically relevant, offering a pragmatic modernization pathway for enterprises balancing innovation with legacy continuity.