Everything we do at GitLab, from our integrated product to our monthly releases, is centered on the goal of helping development teams reduce time to value. With each release, we want to help you do more in less time, while also providing an intuitive and user-friendly experience in our product. GitLab 9.5 takes a big step in furthering this goal. This release features improvements to our navigation, new project templates with pre-configured CI, and new automation features for CI and performance monitoring that will save you time and effort.
This will be the last 9.x release, as we're preparing to release GitLab 10.0 on September 22nd! Nonetheless, we're shipping some great new features to round off our 9.x releases:
Here at Linagora, we believe in open source. If you have read my last article, you should know that we have recently migrated from Atlassian to GitLab.
GitLab CEO Sid Sijbrandij occasionally sits down for a "pick your brain" meeting with people seeking advice on open source, remote work, or discussion of other things related to GitLab.
When we launched Singer, our open source ETL project at Stitch, I was looking for advice on the best strategies to make it successful. August Capital is an investor in both Stitch and GitLab, and they were kind enough to introduce me to Sid Sijbrandij, CEO of GitLab. Sid was very generous with his time, and he shared some of his lessons learned about open source.
Every day from Monday to Thursday, right before our GitLab Team call, a different Functional Group gives an update to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
DevOps is the practice of breaking down silos between Development and Operations teams. DevOps promotes a culture and practices where Dev and Ops teams have open communication and collaboration. This article explains how the Linux Ops team and one of the Development teams at the Government of Nova Scotia were able to implement DevOps practices and realize its benefits.
Every day from Monday to Thursday, right before our GitLab Team call, a different Functional Group gives an update to our team.
The format of these calls is simple and short where they can either give a presentation or quickly walk the team through their agenda.
Today we are releasing version 9.4.5 for GitLab Community Edition (CE) and Enterprise Edition (EE).
This version resolves a number of regressions and bugs in the 9.4.4 release and prior versions.
GitLab CEO Sid Sijbrandij occasionally sits down for a "pick your brain" meeting with people seeking advice on open source, remote work, or discussion of other things related to GitLab.
Navigating growth in a high-tech remote organization can be challenging. CEO of FormAssembly, Cedric Savarese, recently sat down with GitLab CEO Sytse (Sid) Sijbrandij to chat about remote culture, hiring and scaling.
Today we are releasing versions 9.4.4, 9.3.10, 9.2.10, 9.1.10, 9.0.13, and 8.17.8 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain two critical security fixes. The first is a security fix for a vulnerability in git that can be exploited in GitLab to execute arbitrary shell commands. The second security fix addresses the usage of symlinks inside GitLab Export files that could be used to copy the contents of arbitrary repositories.
We strongly recommend that all affected GitLab installations be upgraded to one of these versions immediately.
Note: This is a coordinated release with several other companies and projects, including git itself, which is why it is occuring at 18:00 UTC. As those projects release their updates this release post will be updated with more information.
Please read on for more details.
Once you write your code the next question is, "How do you deploy it?" There are plenty of ways to do it but none of them is perfect. You need to configure external tools, write your own scripts and maybe even do manual command execution every time you want a new version deployed. At GitLab we believe deployment should be an essential part of workflows, like code review and CI. Several months ago we shipped an amazing feature, auto deploy, that should take care of code deployment for you. Finally, I found some time to give it a try.
This September we'll be holding another of our quarterly issue bashes to allow the Community to get involved in helping to squash some issues in the GitLab Community Edition issue tracker. We have over 1500 GitLab contributors, and we are always looking for more people to join in and contribute to the project in any way that they can.
plapadoo is a software startup from Hannover, Germany, providing tailored, high-quality software engineering to their clients. They fill us in on how they chose solutions for their IT infrastructure, including communication, backups, CI/CD and more.