Removing multi-tool barriers to achieve 14 builds a day

GitLab gives Alteryx visibility to increase build speed

Alteryx offers an end-to-end analytics platform that empowers data analysts and scientists to break data barriers, deliver insights, and get to the answer faster. Organizations all over the world rely on Alteryx daily to deliver actionable insights. The end-to-end Alteryx analytics platform enables analysts and data scientists to discover, share and prep data, perform analysis, deploy and manage analytic models.

Alteryx knew their legacy system of using Subversion with Jenkins was not the optimal toolset to accomplish the goal of improving their Software Development Lifecycle. At that time, the repository was more than 500 gigabytes and was filled with legacy code making it difficult to manage.

They wanted to modernize the development experience to improve deployment and build pace. To achieve this they moved to Git, established an enterprise source code repository tool, and improved their CI and CD. They evaluated three tools: GitHub, Perforce and GitLab in this process.

GitLab allowed Alteryx to truly have everything in one place and within one tool. GitLab was selected because it is one place for CI, CD, source code, source code management, code reviews, and security scanning. Having everything in one place also made it easier for them to scale because teams can just be added to GitLab and have all the things that typically take them 3 or 4 months to get set up.

Alteryx began with the Community Edition of GitLab in 2016 but quickly moved to the Enterprise Edition so they could scale. Teams soon realized the value of a single application to manage their work and they more than doubled their planned number of users in the first six months. Alteryx staff are inspired to use it because the CI is baked right into the repository, allowing developers to actively participate in the DevOps process.

GitLab has allowed Alteryx to have code reviews, source control, continuous integration, and continuous deployment all tied together and speaking the same language. This capability allows each commit or merge request to get a code review-which wasn’t previously happening. That code review is tied to a deployment which is tied to a URL and so on and so forth.

The team took a build that was running legacy systems and moved it to GitLab. This build took 3 hours on the Jenkins machine and it took 30 minutes to run on GitLab after it was going. Engineers can actually look at the build and understand what’s going on; they’re able to debug it and make it successful.