Analytics Workspace CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Engineering and product teams can span multiple GitLab groups and projects, yet most of our analytics have traditionally been developed at the project level. This is why we created a workspace where users can aggregate insights across groups, subgroups, and projects. The Analytics workspace will make it easier for teams and leaders to analyze and manage team metrics. The workspace will be available in Core. However, in some cases, specific features will be available to Enterprise Edition customers. As we move to the Analysis workspace, we will ensure that existing project-level analytics functionality is available to Community Edition users when moved to the new workspace. In GitLab 12.3, we are releasing the first iteration of group and project level Productivity Analytics and group-level Cycle Analytics. In subsequent releases, we will enable the selection of multiple groups and subgroups; porting all analytics features for an instance. We would love your feedback and input on the strategy for Analytics/Value Stream Management Documentation Issue

Design Management notifications CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD In GitLab 12.2 we released our initial iteration of Design Management. An important part of continuing to evolve is to ensure users are properly notified about these activities. Conversations in designs will now create To-Do’s for mentioned users and send notifications based on their preferences. This helps to ensure that important feedback isn’t missed and can be actioned. In a future release, we’ll add those conversations to the main discussion tab for an easier conversation flow. Documentation Issue

API for Merge Request Approval Rules CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Approval Rules for Merge Requests allow you to communicate who should participate in code reviews by specifying the eligible approvers and the minimum number of approvals for each. Approval rules are shown in the merge request widget so the next reviewer can easily be spotted. In GitLab 12.3, support for Approval Rules has been added to the API for Projects and Merge Requests. Documentation Issue

Keyboard shortcut for next and previous unresolved discussion CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Reviewing, discussing and resolving feedback is the basis of code review in GitLab. The Jump to next unresolved discussion button makes it easy to quickly jump from discussion to discussion. In GitLab 12.3, the new n and p keyboard shortcuts to move to the next and previous unresolved discussions in Merge Requests make it even more convenient to review changes. Documentation Issue

API to require merge request approval by code owners per branch CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Using merge request approvals to restrict how code is pushed to protected branches is helpful for promoting code quality and implementing compliance controls. But not all merge requests target stable branches, and not all stable branches need the same controls. In GitLab 12.3, it is possible to require code owners’ approval for specific branches (through the API) to prevent directly pushing changes to files with code owners, or merging changes without the code owners’ approval. Note: This feature is only available via the API in GitLab 12.3. In GitLab 12.4 it will be available through the Protected Branch settings. Follow issue #13251 for updates. Documentation Issue

Flexible 'rules' keyword for controlling pipeline behaviors CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Only/except rules in pipelines can have a lot of implicit behaviors, and as more and more are added to your pipelines, it can become very difficult to understand if a given job is going to run or not in different situations. We are introducing a new rules: syntax that will make it much easier to implement and understand complex rules. This syntax is optional and can exist in the same pipeline, but not the same jobs, as the current only/except approach. Documentation Issue

'only/except: external_pull_requests' for external repositories CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD GitLab CI has an “external repos” capability intended to allow customers to use external repos for source control and GitLab for CI/CD. Until now, however, the CI_PIPELINE_SOURCE always showed push because it was based on the pull mirror rather than the source external repo or webhook. This prevented GitLab us from correctly supporting only/except: merge_requests -style options. In the 12.3 release we’ve resolved this limitation. Documentation Issue

Remove container images from CI/CD CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD The GitLab Container Registry allows users to leverage GitLab CI/CD to build and push images/tags to their project. Changes to the Container Registry are made by a service account called “CI Registry User” that is invoked from .gitlab-ci.yml with the predefined environment variable CI_REGISTRY_USER . Previously, this service account could push new tags to the registry, but it lacked permissions to untag images. This prevented branch-specific images from being removed, resulting in additional storage costs and creating difficulty when navigating the registry user interface due to the large number of additional, unneeded tags. In 12.3 we have expanded the permissions of CI_REGISTRY_USER to allow for untagging of images so you can clean up branch-specific tags as part of your regular CI/CD workflow and use GitLab CI/CD to automate your cleanup scripts. This issue is part of a larger epic to lower the cost of the Container Registry by improving storage management. Documentation Issue

CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD You can now ensure DAST only performs active scans against domains which are intentionally configured for DAST scanning. This helps to ensure that DAST active scans are not unintentionally run against domains which could be serving content or being used in a production capacity. There is no change to passive DAST scans, since passive scanning does not potentially negatively impact scanned sites. Documentation Issue

CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD The SAST SpotBugs analyzer has been updated to allow scanning of code written with Java 11. You can enable this by setting the SAST_JAVA_VERSION environment variable in your project. Documentation Issue

Run Pipeline button for Merge Request Pipelines CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Pipelines for merge requests recently introduced a new way to run a pipeline in the context of a merge request, but the only way to trigger a new run of one of these pipelines was through a push. In this release we’ve added a button to start a new pipeline, making it much easier to retry a failed pipeline. Documentation Issue

User-defined CI variables available to docker build with Auto DevOps CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD CI variables allow you to tailor how processes are run to build your application as part of your CI pipeline. Starting in GitLab 12.3, you can extend the availability of user-defined CI variables to the docker build step in Auto DevOps. The data is made available as a new build secret value. List one or more variables using the AUTO_DEVOPS_BUILD_IMAGE_FORWARDED_CI_VARIABLES variable and it will be made available to use in docker build . Documentation Issue

Knative for group and instance-level clusters CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Group and instance-level clusters now support the installation of Knative, the Kubernetes-based platform to deploy and manage serverless workloads. This will allow multiple projects to make use of GitLab Serverless features leveraging a single cluster. Documentation Issue

Line charts for metrics dashboard CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD When it comes to visualizing metrics, oftentimes users would like to choose different types of visualization for specific metrics (e.g., line chart for CPU, area chart for disk space). To help achieve this, we added line charts as a part of our effort to enhance our dashboard offering around monitoring. Documentation Issue

Quick actions to add/remove Zoom meetings on issues CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Synchronous collaboration is a critical part of any fire-fight. We are streamlining the number of steps it takes to spin up a conference bridge and engage all required parties by embedding this functionality, using Zoom, directly in an issue. Once a user has started a Zoom meeting, they can attach it to an issue using a quick action and inputting the Zoom meeting URL (e.g. /zoom https://gitlab.zoom.us/s/123456 ). A button will appear at the top of the issue giving users direct access to the conference bridge. When the incident has resolved, the Zoom meeting can be removed using /remove_zoom . This feature is generally available on GitLab.com and feature flagged for use on self-managed instances. If you are interested in taking advantage of this feature for your self-managed instance of GitLab, operators can enable the issue_zoom_integration feature flag. In next month’s release of GitLab 12.4 we plan to remove the feature flag and make the Zoom Issue integration generally available for all self-managed users. Documentation Issue