So, CI-CD pipeline, I mainly use it after developing the aspect, like suppose if I make some code changes and I use the Android IDE where we have a Git option to commit our changes by writing a commit message and selecting the kind of files that we want to commit. After committing, there is an option to review because I have used the CI-CD pipeline in order to integrate the sonar queue to make sure if there is any sonar link kind of issue. So, after making the necessary changes and observing the changes, whatever the sonar link or the sonar queue is showing me, I will be able to push my changes to the main line GitHub by making use of the safe and secure CI-CD pipeline, which will run through all the scripts, like we have to ensure that we have followed the coding standards, we have implemented the change log, and we have made sure that we have properly handled if else use case scenario, handle the large statements properly. And we have optimized the entire coding scenarios by removing irrelevant, unwanted spaces and lines. We have added relevant operates and make sure that the CI-CD infrastructure runs through all these. When all these is a checkmark or tick box, then only the entire run profile job will run successfully and it will push the code changes into the main Git to my HMI master. That is my remote changes, my changes will be pushed there. This is how I integrated the obvious CI-CD pipeline.
