Petes Linkedin Blog

Today we are releasing version 15.6.3 for GitLab Community Edition and Enterprise Edition. This version resolves a number of regressions and bugs in this month's 15.6 release and prior versions. GitLab Community Edition and Enterprise Edition Add global.image.tagSuffix as a helm values option Makefile: Upgrade Git to v2.35.4.gl1 and v2.37.4.gl1 Important notes on upgrading This version does not include any new migrations, and for multi-node deployments, should not require any downtime . Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-reconfigure file, which is only used for updates . Updating To update, check out our update page . GitLab subscriptions Access to GitLab Premium and Ultimate features is granted by a paid subscription . Alternatively, sign up for GitLab.com to use GitLab's own infrastructure...

Each year, GitLab's Application Security team likes to recap the highlights from GitLab's bug bounty program. It's been a busy 2022 for security teams across the industry, and we have been fortunate to receive a huge number of excellent reports that help us keep GitLab and its customers secure. With the increase we made to our bug bounty award amounts in November 2021 and increased researcher engagement, we've broken a new record by awarding over $1 million USD in bounties during 2022! We wouldn't be where we are without the collaboration of our bug bounty community, and we consider these awards as hugely beneficial and money well spent. 2022 by the numbers Awarded a total of $1,055,770 USD in bounties across 221 valid reports, up from $337,780 last year! Three researchers earned $100,000+ USD across their multiple reports, and another seven earned over $20,000 USD. Received a total of 920 reports from 424 researchers in 2022. Resolved 158 valid reports a...

GitLab’s mission is to make it so that everyone can contribute . While I have been experiencing this mission for three years, I wondered if there was a way to visualize the effect of having everyone contribute over GitLab's history. It turns out there is. An open source project known as Gource can create an animated visualization of the commit history of a repository. I ran it against the GitLab repository and it visualizes 11 years of busy developers contributing over 300,000 commits to GitLab - covered in just under 10 minutes of video. Each node in the visualization is a file and the count of various file types is shown on the left. A big thank you to absolutely everyone who has made contributions to GitLab over the years. Hopefully this visualization helps you have a greater sense of this community. GitLab has recently published the management principles that help enable the "everyone can contribute" mission within GitLab. This new people management framework is ca...

A little while back I wrote about the future of the GitLab Web IDE and our decision to rebuild the Web IDE on top of the open source VS Code project. Our goal: To make it simple for anyone and everyone to contribute, regardless of their development experience. Today, I am happy to announce that we are preparing to launch the new Web IDE experience as a beta, available to everyone, and enabled by default on GitLab.com. Developers and non-developers alike need to be able to contribute from anywhere, across multiple projects, and without context switching or the need to manage a local development environment. The new Web IDE is more user-friendly and efficient, combining VS Code's powerful core features with significantly improved performance and the ability to securely connect to a remote development environment directly from the Web IDE. Start using the Web IDE Beta December 19 I know you're excited to try it. We've been using it internally and it's fantastic. If yo...

ChatGPT has taken the tech world by storm since its launch on November 30 . Media coverage, front page posts on Hacker News, Twitter threads, and videos - everywhere you look, there is another story. The GitLab Slack was no different. In threads across Slack channels, including those for developer evangelism, UX, the CEO, random news, and every space in between, our team was chatting about this exciting new tool. As we got more familiar with the tool, we started to learn about numerous things it can do. Here are a few that we found: It can write poetry about GitLab features. It can write blog posts. It can write unit tests. It gives advice on how to use certain features of GitLab. It conducts competitive analysis. There’s quite a bit more out there, including inventing a new language and building a virtual machine . We can’t recall any technology that has generated more excitement in such a short time. We acknowledge there are ethical and licensing concerns around using AI...

Testing websites, web applications, or generally everything reachable with the HTTP protocol, can be a challenging exercise. Thanks to tools like curl and jq , DevOps workflows have become more productive and even simple monitoring tasks can be automated with CI/CD pipeline schedules. Sometimes, use cases require specialized tooling with custom HTTP headers, parsing expected responses, and building end-to-end test pipelines. Stressful incidents also need good and fast tools that help analyze the root cause and quickly mitigate and fix problems. Hurl is an open-source project developed and maintained by Orange, and uses libcurl from curl to provide HTTP test capabilities. It aims to tackle complex HTTP test challenges by providing a simple plain text configuration to describe HTTP requests. It can chain requests, capture values, and evaluate queries on headers and body responses. So far, so good: Hurl does not only support fetching data, it can be used to test HTTP sessions and XML ...

On January 6, 2023, we will change the default container image used on GitLab Saas Runners on Linux from Ruby 2.5, which is end of life, to Ruby 3.1. If you have specified a container image in your CI/CD job, then there is no impact to you. In other words, your GitLab SaaS CI/CD job will only run in the default container if no image is set for the job in the .gitlab-ci.yml pipeline file. To check, open the log view of a CI job and note the image used. For example, if you have not added an image to your CI job on GitLab SaaS, then the job log will have the following: Using Docker executor with image ruby:2.5 ... If you have not set a container image in your CI job, then after this change, the job will run in a Ruby 3.1 container. How can I check for any build issues on Ruby 3.1? While it is not expected that running a CI/CD job on Ruby 2.5 is incompatible with Ruby 3.1, to check, simply configure the job to run in a Ruby 3.1 container. To do so, edit the .gitlab-ci.yml and ad...