Repository mirroring allows you to replicate Git repositories from one location to another. This makes it easier to work with multiple GitLab instances, like mirroring your team’s work to a customer’s private GitLab instance. Push mirroring also makes it easier to move a project to GitLab from elsewhere, without disruption, by keeping the old repository up to date.
Push mirroring, now available in Core, was previously available in GitLab Starter.
Security reports show which vulnerability may affect your software, but action is needed in order to address these and ensure the security of your product.
With GitLab 10.8, you can create an issue to solve a vulnerability directly from the security report. If it is a false positive, you can also dismiss the entry. This feedback is immediately visible in the report itself.
You can follow the future development of this feature in this epic.
In the Web IDE, files can now be quickly opened using the fuzzy file
finder, making it easier to navigate large projects. The fuzzy
file finder can be opened using the
Cmd + p/
Ctrl + p keyboard shortcut.
Previously, files could only be opened by browsing the file tree.
Changes can now be staged file by file in the Web IDE, allowing you to stage and commit your changes in smaller commits. As you make changes, they are collected in the unstaged changes list. From this list you can select which files to add to the staged changes list, which is the list of changes that will be part of the your next commit.
Many teams use the burndown chart in their projects to track progress over a milestone. But as many of the teams have started to adopt groups and subgroups, folks have also been asking for the same functionality associated with groups.
In this release, we are shipping burndown charts associated with group milestones. Analagous to project milestone burndown charts, a group milestone burndown chart is associated with a group milestone. All issues that are assigned that group milestone will “burndown” throughout that milestone, allowing you to see progress in a visualization. This allows you see the trend of work being completed over time, enabling you to more quickly anticipate any risk of not finishing scoped work and proactively managing that ahead of time.
Group milestone burndown charts allow for both issue count and issue weight in their calculations, just like their project milestone counterparts. Additionally, group milestone burndown charts automatically account for subgroups. If your group has many layers of subgroups with issues assigned to that group milestone, they will all be accounted for in the burndown.
GitLab is often at the heart of an organization’s software delivery lifecycle, so it is important to ensure it is healthy and responsive. We have already added Prometheus metrics to dependencies like Redis and Postgres, and introduced experimental GitLab metrics in 9.3. Since that release, we have instrumented additional portions of our codebase and reduced the impact, and now utilize these metrics to operate GitLab.com.
With these improvements, we are proud to announce that Prometheus monitoring of GitLab is now generally available in 10.8, and will be on by default for all new installations going forward. We have also released a sample Grafana dashboard to easily visualize these metrics.