Engineering

The upgrade to Ruby 2.7 for GitLab involved thousands of deprecation warnings across hundreds of files. Here's how we fixed most of them.

Subtle differences in proxy setting implementations led to surprising problems for a GitLab customer. Here's how we got to the root of it.

Code review is critical to modern software development. We're making it easier by bringing merge request reviews right into VS Code.

This router and transaction manager ensures there are multiple copies of each Git repository available in the event of an outage – no NFS required.

GitLab uses parallel jobs to help long-running jobs run faster.

This post is about a wild discovery made while investigating strange behavior from HAProxy. We dive into the pathology, describe how we found it, and share some investigative techniques used along the way.

Learn@GitLab offers videos and self-driven demos so you can get the most out of GitLab at your own pace.

From building a Web IDE, to our migration to GCP, to tracking down a bug in NFS – these are some of our most popular engineering blog posts.

Working in the open makes it difficult to work on security vulnerabilities before they're disclosed, especially when that openness discloses them early!

Read our example engineering stories from the past two years that show how to use GitLab for you DevOps cycle, including GitOps, CI/CD and more.

Learn how to use GitLab technology to release software faster and with less risk.

We believe deploying to the cloud should be easy and boring. The deployment process is the same regardless of what tech stack you're using so why not automate it?

Read here an introduction on what merge trains are, how to use them and how to incorporate them to your GitLab project.

New to continuous integration? Learn how to build your first CI pipeline with GitLab.

Learn why you should always fuzz test your Rust code, and the code you'll need to do it.