{"id":34683,"date":"2019-10-31T21:59:48","date_gmt":"2019-10-31T18:59:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov\/"},"modified":"2019-10-31T21:59:48","modified_gmt":"2019-10-31T18:59:48","slug":"gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov","title":{"rendered":"GitLab 11.11: several responsibilities for merge requests and improvements for containers.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"GitLab<\/p>\n

<\/p>\n

More collaboration opportunities and additional notifications<\/h3>\n

<\/p>\n

At GitLab, we are constantly looking for new ways to enhance collaboration throughout the DevOps lifecycle. We are excited to announce that with this release we support multiple assignees for a single merge request<\/a><\/noindex>! This feature is available starting from the GitLab Starter level and truly embodies our motto: \u201cEveryone can contribute\u201d<\/strong>. We understand that multiple people may be working on a single merge request to ensure everything is in order, and now you have the ability to assign multiple people to merge requests!<\/p>\n

<\/p>\n

Additionally, DevOps teams now receive automatic notifications about deployment events in Slack and Mattermost<\/a><\/noindex>. Add new notifications to the event sending list in these two chats, and your team will be notified almost instantly about new deployments.<\/p>\n

<\/p>\n

Reducing costs with Docker container support on Windows and preparing Kubernetes clusters at the instance level<\/h3>\n

<\/a><\/noindex><\/p>\n

We love containers! Containers use fewer system resources compared to virtual machines and improve application portability. Since GitLab version 11.11, we support Windows Container Executor for GitLab Runner<\/a><\/noindex>, so now you can use Docker containers on Windows and enjoy enhanced pipeline orchestration and management capabilities.<\/p>\n

<\/p>\n

GitLab Premium (for self-managed instances only) now offers a caching proxy for dependencies for Docker images<\/a><\/noindex>. This addition will speed up delivery, as you will now have a caching proxy for frequently used Docker images.<\/p>\n

<\/p>\n

Users of self-managed GitLab instances can now prepare Kubernetes clusters at the instance level<\/a><\/noindex>, and all groups and projects within the instance will use it for their deployments. Thanks to this integration, GitLab will automatically create resources for specific projects for added security.<\/p>\n

<\/p>\n

And that's not all!<\/h3>\n

<\/p>\n

In addition to new collaboration opportunities and additional notifications, we have added guest access to releases<\/a><\/noindex>, increased additional CI Runner minutes for GitLab Free<\/a><\/noindex>, simplified checks with automatic discussion resolution when you apply a suggestion<\/a><\/noindex>, and much more!<\/p>\n

<\/p>\n

The most valuable player of the month (MVP<\/a><\/noindex>) \u2014 Kia Mei Somabes (Kia Mei Somabes<\/a><\/noindex>)<\/p>\n

In this release, we added the ability to upload individual folders from repositories, rather than all content. Now you can upload just a few necessary files. Thank you, Kia May Somabes!<\/p><\/blockquote>\n

<\/p>\n

Key Features of GitLab 11.11<\/h2>\n

<\/p>\n

Windows Container Executor for GitLab Runner<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

In GitLab 11.11, we added a new executor to GitLab Runner, enabling Docker containers to be used on Windows. Previously, orchestrating Docker containers on Windows required the use of a shell, but now you can work with Docker containers on Windows directly, nearly the same way as on Linux. Microsoft platform users now have more capabilities for orchestrating pipelines and management.<\/p>\n

<\/p>\n

This update includes improved PowerShell support in GitLab CI\/CD, as well as new helper images for various versions of Windows containers. Your own Windows runners can, of course, be used with GitLab.com, but they are not yet part of the publicly available tools.<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Caching dependency proxy for the container registry<\/h3>\n

<\/p>\n

PREMIUM, ULTIMATE<\/em><\/p>\n

<\/p>\n

Teams often use containers in build pipelines, and a caching proxy for frequently used images and packages from upstream is a great way to speed up pipelines. With a local copy of the required layers available through the new caching proxy, you can work more efficiently with popular images in your environment.<\/p>\n

<\/p>\n

So far, the container proxy is available only for self-managed instances on the web server Puma (in experimental mode)<\/a><\/noindex>.<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Multiple assignees for merge requests<\/h3>\n

<\/p>\n

STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

It is quite common for several people to work on a feature in a shared branch and merge request, for example, when frontend and backend developers collaborate closely or when developers pair up, as in extreme programming.<\/p>\n

<\/p>\n

In GitLab 11.11, multiple people can be assigned to merge requests. As with multiple assignees for tasks, you can also use lists, filters, notifications, and the API here.<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Kubernetes cluster configuration at the instance level<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n

<\/p>\n

The security and preparation model in Kubernetes is evolving, and now you can serve a large number of clients through a single shared cluster.<\/p>\n

<\/p>\n

In GitLab 11.11, users of self-managed instances can now prepare a cluster at the instance level, and all groups and projects within an instance will use it for their deployments. Thanks to this integration, GitLab will automatically create resources for specific projects for added security.<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Deployment notifications in Slack and Mattermost<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

You can now configure automatic notifications for deployment events in your team's channel thanks to the integration with chat systems. Slack<\/a><\/noindex> and Mattermost<\/a><\/noindex>, and your team will stay informed about all important events.<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Guest access to releases<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Now, guest users of your projects can view releases published on the Releases page. They will be able to download published artifacts but will not be able to download the source code or see repository details, such as tags or commits.<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Other improvements in GitLab 11.11<\/h2>\n

<\/p>\n

Serialized commit graphs for performance enhancement<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Many Git operations require traversing the commit graph, such as calculating the merge base or outputting branches that contain a commit. The more commits there are, the slower these operations become because traversing requires loading each object from disk to read its pointers.<\/p>\n

<\/p>\n

In GitLab 11.11, we incorporated the serialized commit graph feature introduced in recent Git releases to precompute and store this information. Now traversals in large repositories are significantly faster. The commit graph will be automatically created during the next garbage collection of the repository.<\/p>\n

<\/p>\n

Read about how the serialized commit graph was created in a series of articles<\/a><\/noindex> by one of the feature's authors.<\/p>\n

<\/p>\n

Additional CI Runner minutes: now available for free plans<\/h3>\n

<\/p>\n

FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Last month, we added the ability to purchase additional CI Runner minutes, but only for paid plans of GitLab.com. In this release, minutes can also be purchased for free plans.<\/p>\n

<\/p>\n

Uploading directory archives in repositories<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Depending on the type and size of the project, archiving the entire project can be slow and may not always be necessary, especially in the case of large monorepositories. In GitLab 11.11, you can upload an archive of the contents of the current directory, including subdirectories, to select only the needed folders.<\/p>\n

<\/p>\n

Thank you for your work, Kia May Somabes<\/a><\/noindex>!<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Applying a suggestion now automatically resolves discussions<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

The proposal for changes simplifies collaboration on merge requests: you can now avoid copy-pasting to accept the proposed change. In GitLab 11.11, we made this process even easier: discussions are automatically resolved when applying a suggestion.<\/p>\n

\n

\r\n \"Play\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

Time tracker on the task board sidebar<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Task sidebars should look the same in board and task views. Therefore, GitLab now has a time tracker on the sidebar of the task board. Just go to the task board, click on a task, and the sidebar with the time tracker will open.<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Deployment information in Environments API<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

We added the ability to request information about a specific environment from the Environments API to know which commit is deployed in the environment right now. This will simplify automation and reporting for Environments users in GitLab.<\/p>\n

<\/p>\n

Negative variable matches for pipeline rules<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

It is now possible to check for negative equality or pattern matches (!=<\/code> and !~<\/code>) in the file .gitlab-ci.yml<\/code> when checking environment variable values, so the behavior control of pipelines has become more flexible.<\/p>\n

<\/p>\n

Run all manually executed jobs in a stage with one click<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

In GitLab 11.11, users with many manually executed jobs in stages can now execute all such jobs in one stage by clicking the \"Play all\"<\/strong> (\"Run all\") button next to the stage name in the pipelines view.<\/p>\n

<\/p>\n

Creating a file directly from an environment variable<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Environment variables are often used to create files, especially for secrets that need to be protected and are only accessible in a specific environment pipeline. To do this, you set the variable's content to the file's content and create a file in a job that contains the value. With the new type of environment variable, file<\/code> this can be done in a single step without modifying .gitlab-ci.yml.<\/code><\/p>\n

<\/p>\n

API endpoint for vulnerability information<\/h3>\n

<\/p>\n

ULTIMATE, GOLD<\/em><\/p>\n

<\/p>\n

You can now request all vulnerabilities identified in the project from the GitLab API. This API allows you to create machine-readable lists of vulnerabilities filtered by type, trustworthiness, and severity.<\/p>\n

<\/p>\n

Ability for full dynamic scanning for DAST<\/h3>\n

<\/p>\n

ULTIMATE, GOLD<\/em><\/p>\n

<\/p>\n

In GitLab, you can dynamically test application security (Dynamic Application Security Testing, DAST) as part of the CI pipeline. Starting with this release, you can choose full dynamic scanning instead of standard passive scanning. Full dynamic scanning protects against a greater number of vulnerabilities.<\/p>\n

<\/p>\n

Installing Prometheus in group-level clusters<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

In this release, GitLab introduced the ability to attach a Kubernetes cluster to the entire group. We also added the option to install a single instance of Prometheus on this cluster to simplify the monitoring of all projects on the cluster.<\/p>\n

<\/p>\n

Information about ignoring vulnerabilities on the security dashboard<\/h3>\n

<\/p>\n

ULTIMATE, GOLD<\/em><\/p>\n

<\/p>\n

On GitLab's security dashboards, administrators can view ignored vulnerabilities. To optimize the workflow, we added the ability to view information about ignoring them directly on the security dashboard.<\/p>\n

<\/p>\n

Creating custom metric charts on the dashboard<\/h3>\n

<\/p>\n

PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Create new charts with custom performance metrics directly on the metrics dashboard toolbar. Users can now create, update, and delete metric visualizations on the dashboard by clicking the Add Metric<\/strong> (\"\u0414\u043e\u0431\u0430\u0432\u0438\u0442\u044c \u043c\u0435\u0442\u0440\u0438\u043a\u0443\") in the upper right corner of the dashboard toolbar.<\/p>\n

<\/p>\n

\"GitLab<\/a><\/noindex><\/p>\n

<\/p>\n

Tasks from notifications now open in the name of GitLab Alert Bot<\/h3>\n

<\/p>\n

PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Now tasks created from notifications will have GitLab Alert Bot as the author, so you will immediately see that the task was created automatically from an important notification.<\/p>\n

<\/p>\n

Autosaving epic descriptions to local storage<\/h3>\n

<\/p>\n

ULTIMATE, GOLD<\/em><\/p>\n

<\/p>\n

Epic descriptions were not saved in local storage, so changes were lost unless you explicitly saved them when changing the epic description. In GitLab 11.11, the ability to save epic descriptions in local storage was introduced. This means you can easily return to the epic description edits if an error occurs, if you get distracted, or if you accidentally exit the browser.<\/p>\n

<\/p>\n

Support for mirroring on GitLab for Git LFS<\/h3>\n

<\/p>\n

STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

By using mirroring, you can replicate Git repositories from one location to another. This simplifies the storage of a GitLab replica repository located elsewhere. GitLab now supports mirroring of repositories with Git LFS, so this feature is available even for repositories with large files, such as game textures or scientific data.<\/p>\n

<\/p>\n

Read and write permissions for repositories for personal access tokens<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Many personal access tokens have permissions for changes at the level of api<\/code>, but full access to the API can grant too many rights to some users or organizations.<\/p>\n

<\/p>\n

Thanks to community contributions, personal access tokens can now have read and write rights for project repositories, rather than deeper API access to sensitive areas of GitLab, such as settings and membership.<\/p>\n

<\/p>\n

Thank you, Horatiu Eugen Vlad (Horatiu Eugen Vlad<\/a><\/noindex>)!<\/p>\n

<\/p>\n

Adding basic support for group GraphQL queries<\/h3>\n

<\/p>\n

FREE, BRONZE, SILVER, GOLD, CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n

<\/p>\n

With the GraphQL API, users can precisely specify what data they need and receive all necessary information in a few requests. Starting with this release, GitLab supports adding basic group information to the GraphQL API.<\/p>\n

<\/p>\n

Login with Salesforce credentials<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

GitLab loves Salesforce developers, and to support this community, we allow users to log into GitLab with Salesforce.com credentials. Now instances can be configured to set up GitLab as an application connected to Salesforce, enabling one-click login to GitLab using Salesforce.com.<\/p>\n

<\/p>\n

SAML SSO is now mandatory for web access<\/h3>\n

<\/p>\n

PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

We expanding the single sign-on (SSO) requirement<\/a><\/noindex> at the group level, introduced in version 11.8, with strict resource checks for groups and projects, allowing users to access only when logged in with SAML. This adds an extra layer of access control for organizations that value security and use GitLab.com through SAML SSO. You can now make SSO a mandatory requirement, knowing that users in your group are using SSO.<\/p>\n

<\/p>\n

Filtering by recently created or modified data for epic APIs<\/h3>\n

<\/p>\n

ULTIMATE, GOLD<\/em><\/p>\n

<\/p>\n

It was previously challenging to query recently created or modified data using the epic API in GitLab. In release 11.11, we added additional filters created_after<\/code>, created_before<\/code>, updated_after<\/code> and updated_before<\/code>, to ensure consistency with the task API and quickly find modified or newly created epics.<\/p>\n

<\/p>\n

Biometric authentication with UltraAuth<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Company UltraAuth<\/noindex> specializes in passwordless biometric authentication. We now support this authentication method on GitLab!<\/p>\n

<\/p>\n

Thank you, Kartikey Tanna (Kartikey Tanna<\/a><\/noindex>)!<\/p>\n

<\/p>\n

GitLab Runner 11.11<\/h3>\n

<\/p>\n

CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n

<\/p>\n

Today we released GitLab Runner 11.11! GitLab Runner is an open-source project used to run CI\/CD jobs and send results back to GitLab.<\/p>\n

<\/p>\n