Rapid secret leak detection
It would seem a small mistake to accidentally pass credentials to a shared repository. However, the consequences can be serious. Once an attacker gets your password or API key, they will take over your account, block you, and fraudulently use your money. In addition, a domino effect is possible: access to one account opens access to others. The stakes are high, so it's extremely important to learn about leaked secrets as soon as possible.
In this release we are introducing the option within our SAST functionality. Each commit is scanned in a CI/CD job for secrets. There is a secret - and the developer receives a warning in the merge request. It revokes leaked credentials on the spot and creates new ones.
Ensuring proper change management
As it grows and becomes more complex, it becomes more difficult to maintain consistency between different parts of the organization. The more users of the application and the higher the income, the more serious the consequences of the merge of incorrect or unsafe code. For many organizations, ensuring a proper review process before a code merge is a tough requirement because the risks are so high.
GitLab 11.9 has more control and a more efficient structure thanks to . Previously, to obtain permission, it was enough to specify an individual or group (each member of which can grant permission). Now you can add some rules so that the merge request requires permission from specific individuals or even from several members of a specific group. In addition, the Code Owners feature is integrated into the permission rules, which makes it easy to identify the person who issued the permission.
This allows organizations to implement complex resolution processes while maintaining the simplicity of a single GitLab application where issues, code, pipelines, and monitoring data are visible and available for decision making and speeding up the resolution process.
ChatOps is now open source
GitLab ChatOps is a powerful automation tool that allows you to run any CI/CD job and query its status directly from chat apps like Slack and Mattermost. , ChatOps was part of the GitLab Ultimate subscription. Based ΠΈ , we sometimes move features down a level and never up.
In the case of ChatOps, we realized that this functionality can be useful for everyone, and that community participation can benefit the feature itself.
In GitLab 11.9 we , and as such, it is now freely available for use in self-managed GitLab Core and on GitLab.com and open to the community.
And much more!
There are so many great features available in this release: for example, , ΠΈ - that we can't wait to tell about them!
Most Valuable Employee) of this month is recognized by Marcel Amiro ()
Marcel has been constantly helping us improve the GitLab documentation. He to improve the quality and usability of our documents. Domo arigato [thank you very much (jap.) - approx. trans.] Marcel, we sincerely appreciate it!
Main features added in GitLab 11.9 release
Discovering Secrets and Credentials in a Repository
(ULTIMATE, GOLD)
Developers sometimes inadvertently pass secrets and credentials to remote repositories. If other people have access to this source, or if the project is public, then sensitive information is exposed and can be used by attackers to access resources such as deployment environments.
GitLab 11.9 has a new test called βSecret Detectionβ. It scans the contents of the repository for API keys and other information that shouldn't be there. GitLab displays the results in the SAST report in the merge request widget, pipeline reports, and security dashboards.
If you have already enabled SAST for your application, then you do not need to do anything, just take advantage of this new feature. It is also included in the configuration default.
Rules for resolving merge requests
(PREMIUM, ULTIMATE, SILVER, GOLD)
Code reviews are an integral part of every successful project, but it's not always clear who should be reviewing changes. It is often desirable to have reviewers from different teams: the development team, the user experience team, the production team.
Permission rules allow you to improve the process of interaction between the persons involved in code reviews: the circle of authorized approvers and the minimum number of permissions are defined. The permission rules are displayed in the merge request widget so that the next reviewer can be quickly assigned.
In GitLab 11.8, permission rules were disabled by default. Since GitLab 11.9 they are available by default. In GitLab 11.3 we introduced the option to designate team members responsible for individual codes within a project. The Code Owners feature is integrated into the permission rules so you can always quickly find the right people to review changes.
Moving ChatOps to Core
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
Originally introduced in GitLab Ultimate 10.6, ChatOps has moved to GitLab Core. GitLab ChatOps offers the ability to run GitLab CI jobs via Slack using the feature .
We open source this feature in accordance with our . By using it more often, the community will contribute more.
Function parameters audit
(PREMIUM, ULTIMATE, SILVER, GOLD)
Operations such as adding, removing, or changing function parameters are now logged in the GitLab audit log, so you can see what was changed and when. There was an accident and you need to see what has changed recently? Or do you just need to check how the function parameters were changed as part of the audit? Now this is very easy to do.
Fixing Merge Request Vulnerabilities
(ULTIMATE, GOLD)
To quickly fix code vulnerabilities, the process must be simple. It is important to simplify security patches, allowing developers to focus on their direct responsibilities. In GitLab 11.7 we , but it had to be downloaded, applied locally, and then pushed to a remote repository.
In GitLab 11.9, this process is automated. Fix vulnerabilities without leaving the GitLab web interface. A merge request is created directly from the Vulnerability Info window, and this new branch will already contain the fix. After checking if the issue is resolved, add the fix to the original branch if the pipeline is OK.
Displaying Container Scan Results in the Group Security Dashboard
(ULTIMATE, GOLD)
The Team Security Dashboard allows professionals to focus on what matters most to their work by providing a clear and detailed overview of all possible vulnerabilities that could affect applications. That's why it's important that the dashboard has all the information you need in one place and allows users to explore the data in detail before fixing vulnerabilities.
In GitLab 11.9, container scan results have been added to the dashboard, in addition to the SAST and dependency scan results already available. Now the entire overview is in one place, regardless of the source of the problem.
CI/CD templates for security jobs
(ULTIMATE, GOLD)
GitLab's security features evolve very quickly and require constant updates to keep your code efficient and secure. Changing the definition of a job is difficult when you manage multiple projects. And we also understand that no one wants to take the risk of using the latest version of GitLab without making sure it is fully compatible with the current instance of GitLab.
It is for this reason that we introduced a new job definition mechanism in GitLab 11.7 using .
Starting with GitLab 11.9, we will offer built-in templates for all security jobs: for example, sast ΠΈ dependency_scanning, - compatible with the corresponding version of GitLab.
Include them directly in your configuration and they will be updated with the system every time you upgrade to a new version of GitLab. The pipeline configurations do not change.
The new way to define security jobs is official and does not support any other previous job definitions or code snippets. The definition should be updated as soon as possible to use the new keyword
template. Support for any other syntax may be removed in GitLab 12.0 or other future releases.
Other improvements in GitLab 11.9
Reply to comment
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
GitLab has discussions on topics. Until now, the user writing the initial comment had to decide from the outset whether they wanted a discussion.
We have relaxed this restriction. Take any comment in GitLab (on issues, merge requests and epics) and reply to it, thereby starting a discussion. So the teams interact more organized.
Project templates for .NET, Go, iOS, and Pages
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
To make it easier for users to create new projects, we offer several new project templates:
- Elementary , which includes the base application with CI.
- A ready-to-go template that combines and GitLab CI/CD.
- , ready for initial customization in GitLab. Note that since iOS builds require a dedicated MacOS runner, you will need to provide your own build server if you want to use it with GitLab CI/CD.
- configured to work with Netlify.
Require permission for merge requests from Code Owners
(PREMIUM, ULTIMATE, SILVER, GOLD)
It is not always obvious who approves the merge request.
GitLab now supports requiring you to approve a merge request, depending on which files the request modifies, with . Code Owners are assigned using a file called CODEOWNERS, the format is similar to gitattributes.
Support for automatically assigning Code Owners as persons responsible for approving a merge request has been added in .
Moving Files in the Web IDE
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
Now, by renaming a file or directory, you can move it from the Web IDE to the repository using the new path.
Tags in alphabetical order
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
GitLab tags are incredibly versatile, and teams are constantly finding new uses for them. Accordingly, users often add many tags to an issue, merge request, or epic.
In GitLab 11.9, we've made it a little easier to use labels. In issues, merge requests, and epics, the tags displayed in the sidebar are in alphabetical order. This also applies to viewing the list of these objects.
Quick comments when filtering actions on a task
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
We recently introduced a feature that allows users to filter the action feed by issues, merge requests, or epics, allowing you to focus only on comments or system notes. This setting is saved for every user on the system, and it may happen that a user may not realize that when they view a task a few days later, they see a filtered feed. It seems to him that it is impossible to leave a comment.
We have improved this interaction. Now users can quickly switch to a mode that allows them to leave comments without scrolling back to the top of the feed. This applies to issues, merge requests, and epics.
Reorder child epics
(ULTIMATE, GOLD)
We recently released , allowing you to use epics of epics (in addition to child tasks of epics).
You can now change the order of child epics of epics with a simple drag and drop, as is the case with child tasks. Teams can use order to reflect priority or determine the order in which work is to be completed.
Custom system header and footer messages for web and email
(CORE, STARTER, PREMIUM, ULTIMATE)
We previously added a feature that allows custom header and footer messages to appear on every page in GitLab. She was warmly welcomed, and teams use her to share important information, such as system messages related to their GitLab instance.
We're excited to bring this feature to Core so even more people can use it. In addition, we allow users to optionally display the same messages in all emails sent through GitLab for consistency with a different user interaction point with GitLab.
Filter by confidential tasks
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
Confidential Issues is a useful tool for teams to have private discussions on sensitive topics within an open project. In particular, they are ideal for working on security vulnerabilities. Until now, managing confidential tasks has not been easy.
In GitLab 11.9, the list of GitLab issues is now filtered by sensitive or non-confidential issues. This also applies to searching for tasks using the API.
Thanks for the contribution of Robert Schilling ()!
Editing a Knative Domain After Deployment
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
Specifying a custom domain when installing Knative allows you to serve different serverless applications/features from a unique endpoint.
Now integrating Kubernetes into GitLab allows you to change/update a custom domain after deploying Knative to a Kubernetes cluster.
Checking Kubernetes CA Certificate Format
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
When adding an existing Kubernetes cluster, GitLab now checks that the entered CA certificate is in a valid PEM format. This eliminates potential bugs with Kubernetes integration.
Extending the Merge Request Comparison Utility to the Whole File
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
When reviewing changes in a merge request, it is now possible to expand the per-file diff utility to show the entire file for more context, and leave comments on unmodified lines.
Execution of specific jobs on merge requests only when certain files are changed
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
GitLab 11.6 added the ability to define for pipeline jobs, so that users can only complete specific tasks when creating a merge request.
Now we are expanding this functionality: connection logic has been added , and users can only execute specific jobs for merge requests and only when certain files are modified.
Thanks for the input Hiroyuki Sato ()!
Automatic monitoring of GitLab with Grafana
(CORE, STARTER, PREMIUM, ULTIMATE)
Grafana is now included in our Omnibus package, making it easier to understand how your instance works.
Customize grafana['enable'] = true Π² gitlab.rb, and Grafana will be available at: https://your.gitlab.instance/-/grafana. In the near future we will also "from the box".
View Primary Epics in the Epics Sidebar
(ULTIMATE, GOLD)
We recently introduced , allowing you to use epics of epics.
In GitLab 11.9, we have simplified the mechanism for viewing this relationship. Now not only the parent epic of the given epic is visible, but the entire epic tree in the sidebar on the right. You can see if these epics are closed or not, and you can even go directly to them.
Link to a new issue from a moved and closed issue
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
In GitLab, you can easily move an issue to another project using the sidebar or quick action. Behind the scenes, the existing task is closed and a new task is created in the target project with all the copied data, including system notes and sidebar attributes. This is a great feature.
Given that there is a system note about the move, users, when viewing a closed issue, are perplexed: they cannot help but understand that the issue was closed due to a move.
In this release, we'll indicate right on the icon at the top of the closed issue page that it's moved, and we'll include an inline link to the new issue so that anyone who lands on the old one can quickly jump to the new one.
Youtrack integration
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
GitLab integrates with many external issue tracking systems, making it easy for teams to use GitLab for other functions while keeping their issue management tool of choice.
In this release, we have added the ability to integrate YouTrack from JetBrains.
Thanks for the contribution of Kotau Yauhen ()!
Resizing the merge request file tree
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
When reviewing merge request changes, you can now resize the file tree to display long filenames or save space on smaller screens.
Jump to recent taskbars
(STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD)
Dashboards are very handy, and teams create multiple dashboards for each project and team. We recently added a search bar to quickly filter all the bars you are interested in.
In GitLab 11.9 we also introduced a section Recent in the drop down list. This way, you can quickly navigate to the panels you've recently interacted with.
Ability for developers to create protected branches
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
Protected branches prevent unreviewed code from being moved or merged. However, if no one is allowed to move protected branches, then no one can create a new protected branch: for example, a release branch.
In GitLab 11.9, developers can create protected branches from already protected branches via GitLab or API. The use of Git to move a new protected branch is still limited to avoid accidentally creating new protected branches.
Git object deduplication for open forks (Beta)
(CORE, STARTER, PREMIUM, ULTIMATE)
Forking allows anyone to contribute to open source projects: without write permission, simply by copying the repository to a new project. Keeping full copies of frequently forked Git repositories is inefficient. Now with Git alternatives forks share common objects from an upstream project in an object pool to reduce disk storage requirements.
Fork object pools are only created for open projects if hashed storage is connected. Object pools are enabled via a function parameter object_pools.
Filtering the list of merge requests by assigned approvers
(STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD)
Code reviews are a common practice for any successful project, but it can be difficult for a reviewer to keep track of merge requests.
In GitLab 11.9, the list of merge requests is filtered by the assigned approver. This way you can find merge requests added by you as a reviewer.
We thank Glevin Wiechert for his contribution ()!
Keyboard shortcuts for next and previous file in a merge request
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
When viewing changes in a merge request, you can quickly switch between files using ]or j to move to the next file and [ or k to go to the previous file.
Simplification .gitlab-ci.yml for serverless projects
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
Built on the basis of functionality GitLab CI serverless template gitlab-ci.yml greatly simplified. You do not need to make changes to this file to introduce new features in future releases.
Ingress hostname support
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
During deployment of a Kubernetes Ingress controller, some platforms fall back to an IP address (such as GKE from Google) and others to a DNS name (such as EKS from AWS).
Our Kubernetes integration now supports both types of endpoints to display in the section clusters the project.
Thanks for the contribution of Aaron Walker ()!
Restrict JupyterHub login access to group/project members only
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
Deploying JupyterHub using GitLab integration with Kubernetes is a great way to serve and use Jupyter Notebook in large groups. It is also useful to control access to them when transferring sensitive or personal data.
In GitLab 11.9, the ability to sign in to JupyterHub instances deployed via Kubernetes is limited to project members with developer access (via a group or project).
Customizable time ranges for security panel schemes
(ULTIMATE, GOLD)
The Team Security Dashboard includes a Vulnerability Chart for an overview of the current security status of the team's projects. This is very useful for security directors to set up processes and understand how the team works.
In GitLab 11.9, you can now select the time range for this vulnerability pattern. By default, this is the last 90 days, but you can set the span to 60 or 30 days, depending on the level of detail you want.
This does not affect the data in the counters or in the list, only the data points displayed in the diagram.
Adding an Auto DevOps build job for tags
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
The Auto DevOps auto build step builds your application using the project's Dockerfile or Heroku's build package.
In GitLab 11.9, the resulting Docker image embedded in the tag pipeline is named similarly to traditional image names using a tag commit instead of a SHA commit.
Thanks to Aaron Walker for the input!
Code Climate update to version 0.83.0
(STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD)
GitLab uses to check how changes affect the state of your code and project.
In GitLab 11.9, we updated the engine to the latest version () to provide the benefits of an additional language and static analysis support for GitLab Code Quality.
Thanks for the input from GitLab Core team member Takuya Noguchi ()!
Zooming and Scrolling the Metrics Dashboard
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
When investigating performance anomalies, it is often helpful to take a closer look at the individual parts of a particular metric.
With GitLab 11.9, users will be able to zoom in on individual time periods in the Metrics Dashboard, scroll through the entire time period, and easily revert to the original time period view. This allows you to easily and quickly explore the events you need.
SAST for TypeScript
(ULTIMATE, GOLD)
is a relatively new programming language based on .
In GitLab 11.9, the Static Application Security Testing (SAST) feature analyzes and detects TypeScript code vulnerabilities by exposing them in the merge request widget, at the pipeline level, and in the security dashboard. The current definition of a job sast does not need to be changed, and it is also automatically included in .
SAST for multi-module Maven projects
(ULTIMATE, GOLD)
Maven projects are often organized to bring together in one repository. Previously, GitLab was unable to correctly scan such projects, and developers and security professionals did not receive vulnerability reports.
GitLab 11.9 offers enhanced support for the SAST feature for this specific project configuration, providing the ability to test them for vulnerabilities in the raw state. Due to the flexibility of the analyzers, the configuration is determined automatically, and you do not need to change anything to view the results for multi-module Maven applications. As usual, similar improvements are also available under .
GitLab Runner 11.9
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
Today we also released GitLab Runner 11.9! GitLab Runner is an open source project and is used to run CI/CD jobs and push the results back to GitLab.
Below are some of the changes in GitLab Runner 11.9:
- .
- ΠΈ .
- ... it's the same .
- for support , which will appear in GitLab 11.10.
- .
- .
- Moving multiple scenarios - including ΠΈ β in Go.
- .
- .
- .
The full list of changes can be found in the GitLab Runner changelog: .
GitLab Schema Improvements
(CORE, STARTER, PREMIUM, ULTIMATE)
The following improvements have been made to the GitLab chart:
- Added support for Google Cloud Memorystore.
- Cron job settings because they are used by multiple services.
- The registry has been updated to version 2.7.1.
- A new setting has been added to make the GitLab registry compatible with versions of Docker prior to 1.10. To activate, install
registry.compatibility.schema1.enabled: true.
Performance improvement
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
We continue to improve GitLab performance with each release for GitLab instances of any size. Here are some of the improvements in GitLab 11.9:
- .
- .
- .
- .
Omnibus improvements
(CORE, STARTER, PREMIUM, ULTIMATE)
GitLab 11.9 brings the following Omnibus improvements:
- GitLab 11.9 includes , , whose latest release includes MFA for Team Edition, enhanced image performance, and more. This version also includes ; update recommended.
- A new setting has been added to make the GitLab registry compatible with versions of Docker prior to 1.10. To activate, install
registry['compatibility_schema1_enabled'] = true Π² gitlab.rb. - The GitLab registry now exports Prometheus metrics and is automatically controlled by incoming .
- Added support for Google Cloud Memorystore which requires .
opensslupdated to version 1.0.2r,nginx- up to version 1.14.2,python- up to version 3.4.9,jemalloc- up to version 5.1.0,docutils- up to version 0.13.1,gitlab-monitor- up to version 3.2.0.
Deprecated features
GitLab Geo will bring hashed storage to GitLab 12.0
GitLab Geo is required to mitigate competition (race condition) on secondary nodes. This was noted in .
In GitLab we have added this requirement to the Geo documentation: .
In GitLab sudo gitlab-rake gitlab: geo: check checks if hashed storage is enabled and if all projects are migrated. Cm. . If you are using Geo, please run this check and migrate as soon as possible.
In GitLab permanently disabled warning will be displayed on the page Admin Area βΊ Geo βΊ Nodesif the above checks are not allowed.
In GitLab Geo will use hashed storage requirements. Cm. .
Deletion date: 22th of June 2019
Hipchat integration
Hipchat . Also, in version 11.9 .
Deletion date: 22 March 2019 city
CentOS 6 support for GitLab Runner using Docker executor
GitLab Runner does not support CentOS 6 when using Docker in GitLab 11.9. This is the result of an update to the underlying Docker library that no longer supports CentOS 6. See more at .
Deletion date: 22 March 2019 city
GitLab Runner legacy code paths
Since Gitlab 11.9 GitLab Runner uses cloning/calling the repository. Currently GitLab Runner will use the old method if the new one is not supported.
In GitLab 11.0, we have changed the metrics server configuration view for GitLab Runner. metrics_server will be removed in favor of listen_address in GitLab 12.0. See more in . And more details in .
In version 11.3, GitLab Runner started supporting , which resulted in new settings for . In there is a table of changes and instructions for migrating to the new configuration. See more in .
These paths are no longer available in GitLab 12.0. As a user, you don't need to change anything, just make sure your GitLab instance is running version 11.9+ when you upgrade to GitLab Runner 12.0.
Deletion date: 22th of June 2019
Deprecated option for entry point feature for GitLab Runner
Feature parameter introduced in 11.4 GitLab Runner to fix issues like ΠΈ .
In GitLab 12.0, we will switch to the correct behavior as if the feature setting were disabled. See more in .
Deletion date: 22th of June 2019
Deprecated support for a Linux distribution that has reached EOL for GitLab Runner
Some Linux distributions that you can install GitLab Runner on have served their purpose.
In GitLab 12.0, GitLab Runner will no longer distribute packages to these Linux distributions. A complete list of distributions that are no longer supported can be found in our . Thanks to Javier Ardo) for his !
Deletion date: 22th of June 2019
Removing old GitLab Runner Helper commands
As part of efforts to support had to abandon some of the old commands that are used for .
GitLab 12.0 launches GitLab Runner with new commands. This only applies to users who override . See more in .
Deletion date: 22th of June 2019
Developers can remove Git tags in GitLab 11.10
Deleting or editing version notes for Git tags in unsecured branches has historically been limited to only .
Because developers can add tags and modify and delete unsecured branches, developers should be able to remove Git tags. In GitLab 11.10 to our permissions model to improve workflow and help developers use tags better and more efficiently.
If you want to keep this restriction for maintainers and owners, use .
Deletion date: 22 April 2019 city
Prometheus 1.x support in Omnibus GitLab
Starting with GitLab , the embedded version of Prometheus 1.0 is deprecated from Omnibus GitLab. . However, the metrics format is not compatible with version 1.0. Existing versions can be upgraded to 2.0 and migrate data if needed .
In GitLab version will automatically install Prometheus 2.0 if it hasn't been updated yet. Data from Prometheus 1.0 will be lost because are not transferred.
Deletion date: 22th of June 2019
TLSv1.1
Starting with GitLab to improve security. This fixes numerous issues, including Heartbleed, and makes GitLab PCI DSS 3.1 compliant out of the box.
To disable TLS v1.1 immediately, set nginx['ssl_protocols'] = "TLSv1.2" Π² gitlab.rband and run gitlab-ctl reconfigure.
Deletion date: 22th of June 2019
OpenShift template for installing GitLab
Official - the recommended way to run GitLab on Kubernetes, including .
to install GitLab is deprecated and will no longer be supported in .
Deletion date: 22th of June 2019
Previous definitions of security jobs
With the introduction any previous job definitions are deprecated and will be removed in GitLab 12.0 or later.
Update your job definitions to use the new syntax and take advantage of all the new security features provided by GitLab.
Removal date: June 22, 2019
System Info section in the admin panel
GitLab presents information about your GitLab instance in admin/system_info, but this information may not be accurate.
ΠΡ admin panel in GitLab 12.0 and recommend using .
Deletion date: 22th of June 2019
Source: habr.com