はてなブックマーク

Domain Specific Languages (DSL) are small, focused languages with a narrow domain of applicability. DSLs are tailored towards their target domain so that domain experts can formalize ideas based on their knowledge and background. This makes DSLs powerful tools that can be used for the purpose of increasing programmer efficiency by being more expressive in their target domain, compared to general p

Why we're sticking with Ruby on Rails GitLab CEO and co-founder Sid Sijbrandij makes the case for Ruby on Rails. When David Heinemeier Hansson created Ruby on Rails (interview), he was guided by his experience with both PHP and Java. On the one hand, he didn’t like the way the verbosity and rigidness of Java made Java web frameworks complex and difficult to use, but appreciated their structural in

Improving the performance and reliability of GitLab.com has always been a top priority for GitLab. While we continuously make iterative improvements to GitLab and our production architecture, we anticipate making a larger change to improve the scalability and reliability of GitLab.com: We are splitting our single PostgreSQL database into a main and a ci database. We believe this process, also know

Way back in April 2018, GitLab 10.7 introduced the Web IDE to the world and brought a delightful multi-file editor to the heart of the GitLab experience. Our goal was to make it easier for anyone and everyone to contribute, regardless of their development experience. Since its introduction, tens of millions of commits have been made from the Web IDE, and we've added features like Live Preview and

2022-11-17 UPDATE: User limits will be rolled out gradually, impacted users will be notified in-app at least 60 days prior to the user limits being applied to their top-level group. User limits do not apply to top-level groups with public visibility. If you're running an Open Source project, please also consider the GitLab for Open Source program which can provide more CI/CD minutes as well as add

Ruby 3.0 was just released on Dec. 25, 2020, with some new features and some breaking changes. GitLab was at Ruby 2.6, and we wanted to upgrade to Ruby 2.7 in preparation to eventually upgrade to Ruby 3. In Ruby 3.0, positional and keyword arguments will be separated. To help developers prepare for this, in Ruby 2.7, warnings were added. In GitLab, we discovered we have [thousands of such warnings

Update: This post does not live up to its original title We are building a better Heroku. It shows my own personal experience and reflects poorly on competitors. I am sorry about that. It should have emphasized the building part, we're just starting. The current 5 minute production app doesn't hold a candle to Heroku at the moment. It should have made it clear the goals is to improve the speed wit

Note: We have added release 13.12 to our release schedule. 13.12 is due to ship on 2021-05-22. This will cause the next major release 14.0 to ship in June instead of May as originally stated. The below content has been updated to reflect the new release date for 14.0 of 2021-06-22. Every Git repository has an initial or original branch, which is the first branch to be created when a new repository

If you've used a Web proxy server before, you're probably familiar with the environment variables http_proxy or HTTP_PROXY. You may be less familiar with no_proxy, which provides a way to exclude traffic destined to certain hosts from using the proxy. While HTTP is a well-defined standard, no standard exists for how clients should handle these variables. As a result, Web clients support these vari

HashiCorp announced a new project at HashiConf Digital called Waypoint. Hashicorp Waypoint Hashicorp Waypoint uses an HCL based configuration file to describe how to build, deploy, and release applications to various cloud platforms, ranging from Kubernetes to AWS to Google Cloud Run. Think of Waypoint as if Terraform and Vagrant came together to describe how to build, deploy, and release your app

For about a year now, the infrastructure department has been working on migrating all services that run on GitLab.com to Kubernetes. The effort has not been without challenges, not only with moving services to Kubernetes but also managing a hybrid deployment during the transition. We have learned a number of lessons along the way that we will explore in this post. Since the very beginning of GitLa

We teamed up with OnGres to perform a major version upgrade of GitLab.com's main Postgres cluster from version 9.6 to 11 back in May 2020. We upgraded it during a maintenance window, and it all went according to plan. We unpack all that was involved – from planning, testing, and full process automation – to achieve a near-perfect execution of the PostgreSQL upgrade. The full operation was recorded

It’s been years in the making, but our journey to migrate our application servers from Unicorn to Puma is complete. With the Gitlab 12.9 release Puma was running on GitLab.com and now with 13.0 it is the default application server for everyone. This is the story about how we migrated from Unicorn to Puma and the results we’ve seen. A starting point Both Unicorn and Puma are web servers for Ruby on

The KDE community is #movingtogitlab! After announcing the original decision to migrate to GitLab in November 2019, KDE has officially completed phase one of their migration, and contributors have begun to use GitLab on a daily basis at invent.kde.org. Read on to learn more about KDE's migration story. About KDE KDE is an international community that creates open source software for desktops and m

Sometimes, you can have too much of a good thing. That’s certainly true with Git flow, a well-known software development workflow that offers several options but can bog down users. We developed GitLab Flow as the solution to eliminate messy complexity and streamline the development process. GitLab Flow brings issue tracking to the Git workflow, simplifying the process and removing confusion. The

The Git project began nearly 15 years ago, on [April 7, 2005](https://marc.info/?l=linux-kernel&m=111288700902396), and is now the version control system of choice for developers. Yet, there are certain types of projects that often do not use Git, particularly projects that have many large binary files, such as video games. One reason projects with large binary files don't use Git is because, when

How our QA team leverages GitLab’s performance testing tool (and you can too) We built our open source GitLab Performance tool to evaluate pain points and implement solutions on every GitLab environment. We’ve set up several initiatives aimed at testing and improving the performance of GitLab, which is why the Quality team built a new tool to test GitLab's performance. Performance testing is an in

Tutorial on privilege escalation and post exploitation tactics in Google Cloud Platform environments A Red Team exercise on exploiting design decisions on GCP. Update At GitLab we have an internal Red Team that dedicates time looking at the services and business partners we use to deliver GitLab products and services. As a Google Cloud customer, we have an obvious interest in all the different way

Why GitLab.com is changing its CDN provider to Cloudflare March 28 Get the scoop on our plan to change GitLab.com to Cloudflare. Upcoming changes to our CDN for GitLab.com As GitLab.com has grown, so have our needs around the security and scalability of the web application. We are in the process of changing our CDN provider to Cloudflare as part of our improvements to GitLab.com. We are approachin

This year's survey highlights evolving attitudes towards security, AI, and developer experience. Our survey of more than 5,000 DevSecOps professionals worldwide showed that organizations are prioritizing investments in security, AI, and automation — and all of these are having positive effects on the experiences of developers and software engineering teams. However, this year's survey also highlig

GitLab 12.0 Release GitLab 12.0 released with Visual Reviews and Dependency List GitLab 12.0 released with Visual Reviews, Dependency List, and much more! Dev, Sec, and Ops GitLab 12.0 marks a key step in our journey to create an inclusive approach to DevSecOps, empowering "everyone to contribute". For the past year, we've been on an amazing journey, collaborating and creating a solution that brin

Today at GitHub’s Satellite developer conference, GitHub announced a number of new features. If you are a GitLab user, here is a quick cheat sheet of what GitHub announced today and how that relates to GitLab features that already exist or are on the public GitLab direction page. What GitHub announced on May 23, 2019 Similar & related GitLab features

GitLab 11.11 Release GitLab 11.11 released with Multi-Assignment for MRs and container enhancements GitLab 11.11 released with Multi-Assignment for Merge Requests, Windows Container Executor, Dependency Proxy, and much more! Increased collaboration and visibility One of the areas we focus on at GitLab is to find new ways to increase collaboration throughout the entire DevOps lifecycle. In this rel

Today, Atlassian Bitbucket, GitHub, and GitLab are issuing a joint blog post, in a coordinated effort to help educate and inform users of the three platforms on secure best practices relating to the recent Git ransomware incident. Though there is no evidence Atlassian Bitbucket, GitHub, or GitLab products were compromised in any way, we believe it’s important to help the software development commu

Last June, we had to face the facts: Our SaaS infrastructure for GitLab.com was not ready for mission-critical workloads, error rates were just too high, and availability was too low. To address these challenges, we decided to migrate from Azure to Google Cloud Platform (GCP) and document the journey publicly, end to end. A lot has happened since we first talked about moving to GCP, and we’re exci