How adSoul transitioned to GitLab CI from Jenkins

adSoul, a data-driven online marketing startup from Germany, streamlined its processes by migrating from Jenkins to GitLab CI, primarily to enhance stability, reduce maintenance, and improve visibility. Philipp Westphalen, a fullstack developer at adSoul, shared the three-phase migration journey at GitLab Commit London. The phases included moving the repository, migrating the CI/CD pipeline, and refining the CI/CD processes, which involved overcoming challenges like issue migration and adapting scripts for GitLab API. The team emphasized a strategic, step-by-step approach, involving all team members to ensure a seamless transition. They successfully improved build times and project management by adopting Gradle, parallel job processing, and standard Docker images, while maintaining a user-friendly pipeline environment. The transition to GitLab offered adSoul a highly customizable CI/CD platform that mitigated interdependencies between branches, allowing for exploratory changes without impacting the main job, and significantly reduced maintenance efforts, which was crucial for their small team.

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.