Yes, this is a common for CI CD pipeline for currently that continue integration and continue development for we call the DevOps process and whenever we are developing any application we follow that thing that in our mind we use that normally in coding side GitLab, GitHub for coding purpose and what type of branches we need, which branches we currently developing application, which branches we have that production role and instrument testing through we can already write but if anything is failing any build, build is failing then we know that we using Jenkins server for that plugging we can check the ecosystem and unit test we just check our unit test is working fine, integration testing for working fine, UI test for in it will test we can pass that thing it test we can implement for unit testing and instrument testing for JUnit, Mockito and Expresso for the testing purpose and whenever that implementing and our application is properly run and building then if anything is failed and Jenkins CI CD pipeline is failing we aware of we can just check where is pipeline fail database like room database whatever of database we have UI and end-to-end testing is focusing for Expresso is instrument testing whenever our UI is running with no need to test in manually and we have that pipeline Jenkins server if we are just declaring Jenkins pipeline to our code side and deploy the application then whenever application is going to development side they can identify our that server identify that application is any issue or not monitoring and reporting purpose we have the tools like we have different tool for DevOps we use that test report and sonar cube report and if we have a covert report if we need to code side some security base and we need to analyzing some code thing and cover our code and feedback needed to refactor our code this thing we can use that our current project and anyone is using that CI CD pipeline for development
