Glovo Γ— Mergify

How Glovo deployed Mergify to save time and improve engineers' lives.

Summary

Challenges

  • Efficient Continuous Delivery in back-end.
  • Automate Gitflow-based workflow.
  • Increase engineers' efficiency and happiness.

Solution

  • Configure Mergify to automate their tasks
  • Integrate Mergify to their Gitflow workflow.
  • Leverage merge queues to guarantee merge safetyness.

Results

  • Merge time reduced, faster continuous deployment.
  • Gitflow: automatic merge & automatic backport.
  • Improved developer experience: everyone's happier.

Who's Glovo?

Glovo is a Spanish tech company and the fastest-growing multicategory player in Europe, Western Asia, and Africa. With technology at the core of its business, it creates innovative solutions by connecting customers, companies, and couriers, ensuring a sustainable impact on their communities and ecosystems. Glovo counts a hundred web engineers, two-hundreds mobile/back-end engineers β€” and growing.

Capture d’écran 2022-04-06 Γ  09.28.08.png

Glovo Before Using Mergify

Before using Mergify, Glovo's engineering teams had two main issues.

First, many of their Github repositories receive contributions from hundreds of engineers regularly Every time a developer merges a pull request to the main branch, pull requests need to be updated and rebased to be retested. This creates a bottleneck as engineers need to maintain their pull requests for a long time.

Then, the mobile team uses Gitflow for development. This was not designed with continuous delivery in mind, and it's something that the team wanted to put in place.

That's why they started to look for a tool to automate and secure their merge, by keeping pull requests up-to-date as needed β€” speeding the merge time and reducing CI usage.

They compared multiple solutions and Mergify finally stood out.

The configuration was helpful and reliable, so it was really easy. The only thing hard was to decide what to put in the configuration.

Juan Carlos Arocha - Staff Engineer

Deploying Mergify

Glovo started to build a proof-of-concept using Mergify and demonstrated that it suited their needs for their different types of repositories. After validating the workflow and seeing the potential gain, getting a budget approved and deploying Mergify was the simplest part considering the previous situation.

As Mergify uses GitHub, no big changes were made to the developer workflow. The adoption was straightforward.

Mergify allows Glovo engineering team to:

  • Improve the confidence of engineers with a fully automated workflow.

  • Reduce the time-to-merge of the pull requests. Engineers don't have to click to merge anymore. It makes a faster continuous development.

  • Improve the developer experience. Developers are happier because they don't have to do any work manually.

  • Make their Gitflow workflow more efficient by combining automatic backport and automatic merge.

  • Automate Dependabot. Mergify approves minor/micro versions automatically.

009jz1uf.png

Mergify removes work. Just use it!

Juan Carlos Arocha - Staff Engineer

Glovo Gains With Mergify

With hundreds of engineers working on the same repository and the same branch, trying to manually update and merge pull requests was a nightmare for engineers, clicking simultaneously to merge their pull requests each day, and fighting each other.

Adapting Mergify allowed them to save CI cost and time with the merging process, and avoid developers' frustrations, providing happiness at work.

Now their workflow is fully automated, and they can focus on projects that matter.

Right now, all our repositories that adopted Mergify, have their CIΒ checks completely green! It improves the confidence of engineers.

Juan Carlos Arocha - Staff Engineer

Ready to get started?