Over a hundred iOS engineers work on one app here. Hundreds of pull requests land a day, and even though each one passed CI, main breaks often once they're merged. How would you design CI/CD so main stays green and the release cadence holds?
In a modularized monorepo you verify only the affected targets, share a remote build cache, protect main with a merge queue that validates batches, autoscale the build machine pool, and ship on a fixed release train with feature flags.
Build and distributionShort answerAdvanced
If you designed an iOS CI/CD pipeline from scratch, what steps would the pipeline that…
#ci-cd
Build and distributionShort answerAdvanced
You inherit a project where a clean build takes 15 minutes and a one-line change still…
#modularization
Build and distributionShort answerExpert
A team on an app with more than a hundred modules is drowning in project.pbxproj…
#monorepo
Build and distributionShort answerAdvanced
This one comes up onsite. "If you had to pick between a monorepo and several small…
#monorepo