Ruchir Garg, Red Hat
Continuous Integration is the need of the day for dynamic software, where time to market is the key. To achieve this, it’s necessary that all incoming code merge requests meet the quality criteria and doesn’t break the master build. These checks cannot be only manual, and hence all repetitive steps need to be automated.
This paper talks about automated checks that ensure that the incoming code meets the recommended coding guidelines contains enough unit tests, references the feature it adds or the issue it fixes, maintains backward compatibility, contains documentation (if needed), etc. The comprehensive list of possibilities is dependent on the criteria defined by the team. Failure to meet such criteria results in rejected merge request.
Once these checks pass, the reviewer has to only review the code and the artifacts of the automation manually. This cuts down on the review time and prevents time wastage. It also helps to keep the quality quotient high and the software deployment ready.