Kubernetes is now the industry standard for container management and orchestration. Containers are a perfect match for CI/CD in both build and test environments, since they can be quickly initiated, versioned, and rapidly shutdown. It has become common to use Kubernetes with compatible Continuous Integration (CI) processes and tools. One of these tools is Jenkins.
Build Automation Benefits:
Speed horizontal scaling by jumpstarting the worker node build process
Recover instantly from test errors or failed configuration changes
Save time and resources when operating across multiple Kubernetes clusters, multiple clouds, and hybrid deployments
Reduce costs for CI/CD by up to 50% compared to legacy storage solutions
Customers face numerous challenges distributing the load across multiple worker nodes in a Jenkins environment. In a standard Jenkins workflow, each worker node creates its own environment from scratch. This approach, which requires a full repository copy and a complete build, slows horizontal scaling and increases build / test time.
Also, if a worker node does not start from a clean state, tests are more likely to fail, further increasing overall test time.
When Jenkins spans multiple clouds, the above issues increase exponentially.
Running ionir as the Jenkins data platform allows more rapid and efficient scaling of CI/CD pipelines across multiple clouds and data centers. Rather than each node pulling resources and creating its own environment, ionior allows operators to instantly clone ‘golden images’ to jump start the build process and speed horizontal scaling. ionir’s persistent, resilient, and high-performance storage cuts run times for builds and tests in both monolithic and scaled Jenkins environments.
In environments with multiple worker nodes, and when operating across clouds, ionir’s instant point-in-time clones and rapid data movement simplify workflows, speed on-demand scaling, and increase testing reliability. Benefits include lower OPEX, up to a 50% reduction in CI/CD infrastructure, and faster time to delivery for applications.
ionir’s Kubernetes native storage platform is ideal for containerized Jenkins implementations. Data agility, including the ability to move any size volume to any location in 40 seconds, and the ability to instantly restore 1-second RPOs significantly accelerates workflows that require data to be preserved and copied.
"Container-native storage holds real promise for ensuring Kubernetes data persistence, while enabling convergence and automation of myriad data protection and management services IT typically has to cobble together now."
Rich Arsenault, VP Infrastructure and Services, Mimecast
"ionir delivers a converged, container-native data layer for Kubernetes. This fresh approach replaces dozens of isolated products and processes that evolved to serve the needs of non-containerized environments."
Jacob Cherian, CEO of ionir
"The core technology behind ionir was 8 years in development. Two intersecting areas of innovation set the approach apart from all other attempts at container native data and storage management. First is a new approach to metadata that allows instant mobility of data in both place and time. The second is a microservices architecture that isolates core processing from external interfaces enabling extensibility and scale."