possible ▸ Validates changes using automated tests ▸ Added advantage over delayed merges which usually ends up in integration hell ▸ Always checks newer commits doesn’t break any of the existing code CI PIPELINE
changes quickly in a sustainable way ▸ Deploy at your convenience time (daily, weekly, fortnightly) ▸ Best practice is to rollout updates in small batches for ease troubleshooting any production issues. ▸ Continuous Deployment is the automatic version of Continuous Delivery. CD PIPELINE
coverage metrics ▸ You can exercise your frameworks (only open source files) ▸ You can customise running certain TestBundles on Certain Targets XCODE CODE COVERAGE