Why we chose GitLab CI for our CI/CD solution

OOHLALA Mobile, an education technology company, implemented GitLab CI as their CI/CD solution to manage the deployment of their increasingly complex fabfile system, which is primarily executed through Fabric. They favored GitLab CI for its simplicity, speed, and cost-effectiveness, especially given their small development team and need for tailored solutions on dedicated hardware. Unlike other CI solutions such as Jenkins, Travis CI, and CircleCI, GitLab CI's shell executor was ideal for executing fabfiles quickly, without the overhead of Docker dependency setups. The flexibility of installing GitLab runners on their own macOS and Windows machines for mobile app CI/CD was a significant advantage, allowing them to maintain control over their infrastructure and keep SSH keys secure. Ultimately, the seamless integration with GitLab CI influenced their decision to host their code on GitLab.com, as other hosting services like GitHub and Gogs did not offer significant feature advantages for their needs.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.