Gitaly is a Git RPC service that we are currently rolling out across GitLab.com, to replace our legacy NFS-based file-sharing solution. We expect it to be faster, more stable and the basis for amazing new features in future.
We're still in the process of porting Git operations to Gitaly, but the service has been running in production on GitLab.com for about 9 months, and currently peaks at about 1000 gRPC requests per second. We expect the migration effort to be completed by the beginning of April at which point all Git operations in the GitLab application will use the service and we'll be able to decommission NFS infrastructure.
In this month's release of GitLab 10.4 – the first of 2018 – we've added capabilities to improve planning, testing, merge requests, and deployment. This release also includes new security testing capabilities and the first iteration of our Web IDE, part of our ambitious product vision for Complete DevOps.
Today we are releasing versions 10.3.5, 10.2.7, and 10.1.7 for GitLab Community Edition (CE) and Enterprise Editions (EES, EEP).
These versions resolve a regression causing an error when running migrations on MySQL database, which was introduced on the latest security release patch.
If your version of continuous integration is just daily builds, ignoring failed tests, or not testing at all, you're doing it wrong.
Today we are releasing versions 10.3.4, 10.2.6, and 10.1.6 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain a number of important security fixes, including two that prevent remote code execution, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately.
This security release blog post is the first part of two. The second blog will be posted in approximately 30 days, and it will detail the vulnerability findings.
Please read on for more details regarding this release.
On Tuesday, January 16th, 2018 at 23:59 UTC, we will publish a critical GitLab security update. More details will be forthcoming on our blog, including which versions of GitLab are affected.
We recommend installations running affected versions to upgrade immediately. Please forward this alert to the appropriate people at your organization and have them subscribe to Security Notices.
In GitLab 10.3 we released a new feature: Merge Request Commit Discussions. This is great news for teams who work at the individual commit level, who want to be able to discuss and collaborate on different commits within one merge request. Watch the video below to see this new workflow in action.