December 8, 2020

Standardized CI/CD Pipelines Across Teams

Table of Contents

Key takeaway

About LogMeIn

LogMeIn, Inc. (NASDAQ: LOGM) simplifies how people connect with each other and the world around them to drive meaningful interactions, deepen relationships, and create better outcomes for individuals and businesses. One of the world’s top 10 public SaaS companies, and a market leader in communication & conferencing, identity & access, and customer engagement; support & solutions, LogMeIn has millions of customers spanning virtually every country across the globe. LogMeIn is headquartered in Boston with additional locations across North America, Europe, Middle East, Asia, and Australia.

Standardizing CI/CD Pipelines

Like many organizations, LogMeIn has been in the process of standardizing its Continuous Delivery process across teams, with a view to consolidating its toolsets. An internal initiative was kicked off, and Kyle Flavin, Sr. Staff Engineer at LogMeIn was tasked with making this happen.

Legacy tool deployments were becoming too complex to manage in legacy & modern environments. Complexities with various home-grown deployment frameworks mainly support and maintenance. Automated deployments using the existing CI tool were scripted using pipeline global libraries.
Onboarding new microservices could take a week or more for teams.

Harness is like having a dedicated development team focused on CD for us

Kyle Flavin | Staff Software Engineer | LogMeIn

Evaluating Spinnaker and Harness

LogMeIn evaluated commercial and open-source tools and selected Harness for ease of install, use, and adoption.

“When I got started with Harness it literally took 1-hour to onboard my first service,” said Kyle Flavin, Staff Software Engineer at LogMeIn. “One of our dev teams ran with Harness on their own and was in production within a week,” said Kyle.

When I got started with Harness it literally took 1 hour to onboard my first service.

Kyle Flavin | Staff Software Engineer | LogMeIn

Today, development teams at LogMeIn get self-service Continuous Delivery with standardized deployment pipelines for their microservices.

The Harness CD abstraction model (CDAM) means LogMeIn teams can install, use and onboard in 1-hour regardless of their service container orchestrator or cloud infrastructure.

In addition, teams leverage Harness Canary Deployments and Continuous Verification to automate QA testing, health checks, and deployment verification so that performance anomalies and error regressions can be pro-actively identified in any environment by the deployment pipeline, and if need, code can be automatically rolled back.

One of our dev teams ran with Harness on their own and was in production within a week

Kyle Flavin | Staff Software Engineer | LogMeIn

Harness also provides complete audit capabilities and deployment dashboards to give teams instant visibility and feedback on who deployed what, where.

Reducing Deployment Time, Toil, and Effort

Since migrating to Harness, LogMeIn has seen deployment time drop by 98% from 10-12 hours per deployment to around 30 minutes. Deployment effort (# of people/hours) also dropped from 120 hours per deployment to just 2 hours. Onboarding time went from 1 week to just 1 hour representing a 98% reduction.

You might also like
No items found.

Similar Blogs

No items found.
Continuous Delivery & GitOps