The Real Job Behind the CI/CD Hype

Max Lynch, the Ionic founder, framed it well: every production mobile app carries a recurring workload around integration, testing, deployment, and long-term upkeep. Those tasks need automation across a team and many projects, and building that pipeline can eat time and demand specialized infrastructure experience — yet it's decisive for any serious app project.

That's what "Continuous Integration and Continuous Deployment," or CI/CD, means in practice. And it's precisely why every vendor wants you on their service: it's a powerful form of lock-in. The work is hard enough that any help is welcome, but each provider solves the problem in its own proprietary way. Leaving means redoing a chunk of your setup yourself.

Everyone Has a Pipeline Pitch

The CI/CD landscape is crowded, and the options span from focused newcomers to established workhorses. A quick survey of what crosses our radar at Tech Report:

  • Ionic's AppFlow is a CI/CD entry aimed at mobile teams; we haven't evaluated it, but it presents well.
  • Semaphore is another service we've seen but not yet tested hands-on.
  • At CSS-Tricks, we rely on Buddy for our builds.
  • CodePen's own journey has been instructive: we started with Capistrano, migrated to CodeShip, then GitLab (used for DevOps), and now run GitHub Actions configured through Pulumi. That came only after evaluating Azure DevOps and AWS CodeBuild, with tools like Serverless helping move code to AWS along the way.
  • Netlify handles builds for any Jamstack project we do; its build system is highly configurable, with deployment treated as a given.
  • Brian Leroux joined us on ShopTalk to talk about Begin, a serverless take on CI/CD.
  • The long-standing classics remain Jenkins, Travis CI, and Circle CI.

This list barely scratches the surface — dozens more vendors compete here. Heroku deserves credit for setting expectations early: it taught developers that CI/CD should be Git-based, as straightforward as git push heroku master.

Why the Ecosystem Looks This Way

It's not hard to see why the market is so aggressive. Every vendor wants your secrets stored in their vaults and your permissions configured in their interface. Once you're invested, the switching costs rise sharply alongside the accumulated configuration and process history. The convenience of a polished, turnkey pipeline is real — but it's worth remembering that the convenience is also the hook.