Key points are not available for this paper at this time.
The demand for a robust delivery system for code and updates is increasing every day. Organizations are developing new ways to streamline the processes, so they can increase the efficiency of the project development, by using the automation in various steps such as testing, deployment, project monitoring which allows to remove the dependency on manual work, where the sharing of the progress of various development processes can cause to slow down the development cycle. Original Equipment manufacturers(OEM's) are not an exception with this fast-changing technology and industry shifting towards more software automobile solutions. They are also developing various tools to better deploy the software updates to vehicles in the field such as Continuous Integration Continuous Deployment(CI/CD) pipeline for the smoothing out of the software rollouts. The integration of Continuous Integration and Continuous Delivery (CI/CD) practices within Agile methodologies forms a symbiotic relationship that significantly enhances the efficiency of project delivery. In Agile, where iterative development and rapid releases are key, CI ensures continuous integration of code changes, fostering collaboration and early issue detection. Automated testing, a cornerstone of Agile, is seamlessly integrated into the CI/CD pipeline, providing rapid feedback to developers and maintaining high-quality software throughout development. The deployment phase, automated through Continuous Delivery, aligns with Agile's commitment to delivering valuable software frequently. Together, Agile's iterative approach and CI/CD's automation create a dynamic environment that promotes collaboration, responsiveness to change, and the swift delivery of working software. This cohesive integration of Agile principles with CI/CD practices establishes a foundation for teams to adapt, innovate, and consistently deliver customer value. The initial phase is the integration phase in which the Jenkins CI server will be used with various tools such as GitLab and Jira to start the development phase of the project. Using Jira as a monitoring tool and GitLab as a source management tool a new software can be developed in a fast way. Once the initial development is done, the next phase is testing where static tests and various other tests are automated using Xray. Once the testing is successful the project moves to deployment phase where the project is deployed to consumers using tools such as Jfrog artifactory and AWS EKS. Using a combination of these methods will allow to successfully deploy codes to the users with minimal intervention reducing the chances of error.
Ankit et al. (Mon,) studied this question.