Summary
In this chapter, we concentrated on crafting the CD pipeline code. We learned how to interact programmatically with GitHub and Argo CD using Jenkins pipeline code and conducted performance testing using k6, a straightforward performance testing tool. In the concluding stages, we engaged in the actual deployment, triggering a CD pipeline. Watching CD unfold, we scrutinized changes in the Helm chart and validated the deployments in both the staging and production environments. This chapter concluded with a hands-on demonstration of visualizing performance testing results, ensuring our proficiency in both the theoretical knowledge and practical skills essential for creating a robust CD pipeline.
In the upcoming chapter, we’ll delve into advanced CI/CD pipeline strategies. We’ll master the art of designing efficient pipeline templates using Jenkins shared libraries, guaranteeing streamlined and standardized configurations. Additionally, we’ll explore how...