A bit on ci/cd

While "website" might be a more fitting term than "mobile app" in some contexts, Max Lynch's perspective on CI/CD remains insightful: production mobile apps (and, by extension, websites) require automated processes for integration, testing, deployment, and ongoing maintenance. This automation, crucial for large projects, often demands significant time investment and specialized infrastructure knowledge.

The CI/CD tooling landscape is saturated with vendors, each vying for your business. This competition is understandable; CI/CD is complex, and simplifying it is valuable. However, this simplification often comes with vendor lock-in. Switching providers can be a major undertaking.

My experience with CI/CD highlights this diversity:

• Ionic's AppFlow and Semaphore are visually appealing options, though I haven't personally used them.
• I utilize Buddy for CSS-Tricks.
• CodePen's journey involved Capistrano, CodeShip, GitLab (DevOps), and currently GitHub Actions (with Pulumi), after evaluating Azure DevOps and AWS CodeBuild. We leverage tools like Serverless for AWS deployments.
• Netlify handles my Jamstack projects, providing highly configurable builds and streamlined deployments.
• Brian Leroux's Begin offers a serverless CI/CD approach.
• Jenkins, CircleCI, and Travis CI remain established players.
• Heroku deserves recognition for its early emphasis on Git-based, simplified CI/CD ("git push heroku master").

This list is far from exhaustive; numerous other companies offer CI/CD solutions. The common thread is the desire for control over your project's secrets, permissions, and overall workflow.

The above is the detailed content of A bit on ci/cd. For more information, please follow other related articles on the PHP Chinese website!