TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Ruby Ecosystem Support and Contributions

4 posts · Oct 2018 – Jul 2022

What this trail covers

GitLab actively supports and contributes to the Ruby ecosystem, recognizing its importance for developers and companies using Ruby. This includes becoming a member of Ruby Together to fund critical infrastructure like Bundler and RubyGems.org, and exploring further contributions to community projects like RubyBench.org. This initiative aims to ensure the stability, performance, and continued development of essential Ruby tools and services, benefiting the entire community. The platform also leverages the Ruby on Rails framework for building complex applications, benefiting from its opinionated structure, extensive gem ecosystem, and best practices that guide development towards high quality and consistency. Challenges with Ruby's performance in production are addressed by rewriting critical components in Go and optimizing memory usage through multithreading.

All GitLab trails
  1. Why we're sticking with Ruby on RailsThis post explains the rationale behind GitLab's continued use of Ruby on Rails, highlighting its benefits for approachability, productivity, and modularity. It contrasts Rails' 'modular monolith' approach with the complexities and potential pitfalls of microservices, advocating for the former as a more pragmatic solution for most organizations. The post also touches upon how Rails' architecture supports GitLab's open-core business model by providing a well-structured codebase for community contributions. Performance-critical components are identified as areas where other technologies (Go for Gitaly, PostgreSQL for persistence) are leveraged, demonstrating a pragmatic approach to technology choices.
  2. How we automatically fixed thousands of Ruby 2.7 deprecation warningsThis post details the technical approach taken to automatically fix thousands of Ruby 2.7 deprecation warnings related to keyword arguments. It describes the use of the Deprecation Toolkit gem with RSpec tests to capture runtime warnings and the development of a custom RuboCop check (`Lint/LastKeywordArgument`) to statically analyze and autocorrect these warnings. The integration of this check into GitLab CI pipelines using artifacts is also explained, enabling centralized reporting of remaining warnings.
  3. Why we use Ruby on Rails to build GitLabThis post details the rationale behind choosing Ruby on Rails for building GitLab, highlighting its strengths in enabling high-quality functionality, consistency through best practices, and a rich gem ecosystem. It also discusses challenges related to Ruby's production performance and memory usage, and how these are being addressed by rewriting critical parts in Go (leading to Gitaly) and pursuing multithreading. The post emphasizes how Rails' opinionated structure aligns with GitLab's mission of enabling everyone to contribute by making the codebase more accessible to new developers.