Page 3 - Pip

Why CI/CD?

 In order to minimize the risk to deploying problematic code, a robust and comprehensive
set of automated tests need to be in place.

 This ensures that new code being merged into the main branch (and subsequently

deployed) is deployment ready and bug-free.

 In doing so, software development teams can automate their workflow processes, and do

away with the need of manual deployment.

 This makes it easy for teams to release their new builds to production, encouraging small
and incremental builds, rather than all at once, thus reducing the risk of each

deployment.