GitLab 11.4 came out with a review of merge-requests and pluggable features

 3r31251. 3r3-31.
GitLab 11.4 came out with a review of merge-requests and pluggable features 3r31240. 3r31233.  3r31251.
We are pleased to present a new release of GitLab 11.4 with long-awaited updates designed to help teams work more efficiently. Most teams that use DevOps tend to shorten the delivery cycle time. Therefore, developers are always happy to improve, which will reduce the amount of work and loss in time, because this accelerates the delivery of the product and improves business performance. 3r31240. Connected features (feature flags, feature toggle) . Auto DevOps and CI work better in conjunction with migration of PostgreSQL databases and incremental scheduled deployment 3-33-3393. . Even Git is now faster with support for the
protocol. Git v2 3r31239. . 3r31240. 3r31233.  3r31251.
Review code 3r33535. 3r31233.  3r31251.
3r3334. Review of Merge Requests 3r31239. will help organize comments by code and merge requests. Batch comments (batch comments) allows the reviewer to write comments on the code or merge-requester and then issue and send them in one package, and now tracking changes in the project has become easier. 3r31240. 3r31233.  3r31251.
The key step to delivering a high quality code is to make the right choice of people responsible for reviewing and confirming changes in the code. Taking as a basis the owners of the code entered in release 11.3 (3r340. The original article 3r31239.,
Translation
), GitLab now offers those indicated in file 3r31198. CODEOWNERS , as reviewers and confirmatory for merzh-request. Thus, review and confirmation of changes will be carried out faster and more efficiently. This is also useful for separating roles and responsibilities in a team, for example, if you need specific reviders for specific parts of the code. 3r31240. 3r31233.  3r31251.
The presentation of the Merge-Requester changes in the form of a file tree also makes it easier for the reviewers to view the many changed files and provide their feedback. 3r31240. 3r31233.  3r31251.
Russell Levy, co-founder and CTO of 3r3354. Chorus.ai
, told how the review of merge-requests and the tree view of files help their team: 3r31240. 3r31233.  3r31251.
3r33434. We conduct the code review very carefully and usually write 10-20 comments on the average merge requester, and for some of them several iterations of discussions arise. The Merge Requests Review reduces chaos and hitch during the review code process. 3r33430. 3r31233.  3r31251. 3r31233.  3r31251. 3r33434. For large merge-requests, the new representation of changes in the form of the file tree greatly facilitates and speeds up the review, allowing you to easily navigate the code to understand the dependencies. 3r33430.
3r31233.  3r31251.
Connected features 3r33535. 3r31233.  3r31251.
We present the alpha version of the functionality switching system - 3r376. plug-in features
. Now teams can practice continuous delivery (delivery), adding new features to production in small batches, reducing the risk before full deployment. 3r31240. 3r31233.  3r31251.
Improvements for Auto DevOps and CI /CD 3r33535. 3r31233.  3r31251.
We derive the possibility of r3r386. 3r31198. connection of additional files to the .gitlab-ci.yml file using r3r31198. include 3r31239. from Starter to Core, making it available to all users. All teams can now take advantage of this best practice and manage their CI /CD pipelines more efficiently. 3r31240. 3r31233.  3r31251. 3r395. And even more improvements
3r31233.  3r31251.
Together with the huge GitLab community in this release, we added a lot of amazing improvements, including a new profile page view, quick access to status, highlighting references to 3r31198. @ named , new fast action and the ability to close the epic. 3r31240. 3r31233.  3r31251.
Read on and you’ll learn about all the new features of GitLab 11.4. 3r31240. 3r31233.  3r31251.
3r31-10. We invite you to our meetings 3r31239. and 3r33112. on webcast release ???r31239. . 3r31240. 3r31233.  3r31251.
3r3118. 3r31240. 3r31233.  3r31251. 3r3122. MVP this month is Luke Piccia 3r33535. 3r31233.  3r31251.
Luke added feature. Download file recovery codes for two-factor authentication 3r31239. That will simplify their backup. These codes will be required to log in to your GitLab account if you lose access to your phone or one-time secret password. 3r31240. 3r31233.  3r31251.
Thank you, Luke, for this contribution! 3r31240. 3r31233.  3r31251. 3r33140. The main features of the release of GitLab ???r33535. 3r31233.  3r31251. 3r3144. Review of Merge Requests 3r33535. 3r31233.  3r31251.
(PREMIUM, ULTIMATE, SILVER, GOLD) 3r312340. 3r31233.  3r31251.
Merge Requests Review is a powerful feature of GitLab. Team members lead discussions tied to specific lines of code in the differential, and can even solve them. However, this process can become difficult in merge-requests with large diffs. Often the reviewer has to leave 10 or more comments in one discussion, and the 9th or 10th comment may make previous comments unnecessary. As a result, the author of a merge-request receives a lot of notifications, and he has to deal with everyone. 3r31240. 3r31233.  3r31251.
In this release, we present the Merge Requests Review. This will allow the reviewer to write as many comments to the draft as he needs, make sure they are all necessary, and then send them in one action. Since drafts are saved in GitLab, the reviewer can divide his work into several sessions, for example, start a review on his desktop at work and finish it in the evening at home on a tablet. When these draft comments are sent, they are displayed as normal individual comments. This will give individual team members the opportunity to review the code as it is convenient for them, but still with the entire team. 3r31240. 3r31233.  3r31251.
In future releases, we will improve this feature and provide an opportunity to see 3r3161. preview 3r31239. before posting a batch of comments, as well as grouping notifications about these comments in 3r3163. one notice 3r31239. . 3r31240. 3r31233.  3r31251.
3r31240. 3r31233.  3r31251.
3r3174. Discussion documentation r3r31239. and 3r3176. original ticket
. 3r31240. 3r31233.  3r31251. 3r3181. Creating and using pluggable features in your applications (alpha version) 3r353535. 3r31233.  3r31251.
(PREMIUM, ULTIMATE, SILVER, GOLD) 3r312340. 3r31233.  3r31251.
This feature allows you to create plug-in features for your software and manage them directly in the product. Simply create a new plugin feature, confirm it in your software using simple API instructions, and you will be able to control the behavior of your product in the field using the plugin feature in GitLab itself. 3r31240. 3r31233.  3r31251.
Plug-in features offer a functionality switching system for your application. It will allow teams to achieve continuous delivery (CD), sending new features in production in small batches for controlled testing, sharing sending features with launch for customers. 3r31240. 3r31233.  3r31251.
At the moment, this system is presented in alpha version. We suggest that you check how it works and leave feedback, but do not forget that the implementation may change in future releases. 3r31240. 3r31233.  3r31251.
3r3202. 3r31240. 3r31233.  3r31251.
Documentation on plug-in features and 3r3209. original ticket
. 3r31240. 3r31233.  3r31251.
File tree for viewing merge-request changes 3r3353535. 3r31233.  3r31251.
(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31233.  3r31251.
Code review is a necessary practice for any successful project, but from the list of changes it can be difficult to understand what has changed. To facilitate this task, GitLab now provides a tree of files for changes that you can search by. 3r31240. 3r31233.  3r31251.
The file tree displays the structure and size of changes, as it already works with diff-stats by providing a general outline of changes and improving navigation between diffs. A search through the tree gives the viewers the opportunity to limit themselves to part of the files along the path or file type, simplifying the review by specialists who want to focus only on the part of the merge request. 3r31240. 3r31233.  3r31251.

Previously, the list of modified files was available through a drop-down list with a search that was best suited to go to a specific file. 3r31240. 3r31233.  3r31251.

3r31240. 3r31233.  3r31251.

Documentation on merge-requests and navigation in diff 3r31239. and original ticket . 3r31240. 3r31233.  3r31251.

Code owners are offered as confirming merge requisition 3r3353535. 3r31233.  3r31251.

(STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD) 3r31240. 3r31233.  3r31251.

It is not always obvious who will be the best candidate to review your changes. Code owners are now offered as confirmation when creating or editing a merge-request to simplify the assignment of the right people to this role. 3r31240. 3r31233.  3r31251.

Support code owners appeared in the release of GitLab 11.3 (3r33262. Original article 3r31239., 3r33232. Translation 3r31239.). In future releases, the degree of participation of code owners in merger-request workflows will increase from 3 to 3266. automatic appointment as confirming 3r31239. and required proof of ownership . 3r31240. 3r31233.  3r31251.

3r31240. 3r31233.  3r31251.

Merchant Requests Documentation 3r31239. and

and 3r33310. original ticket . 3r31240. 3r31233.  3r31251. 3r33333. Display and change of status in the user menu 3r33535. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

In the release of GitLab 11.2 (3r3-3324. Original article 3r?12339., [leech=https://habr.com/post/422473/#lichnye-statusy-v-profile] Translation ) We first presented the user statuses, providing the opportunity to share your current workload, mood, or at least your favorite animals. 3r31240. 3r31233.  3r31251.

In this release, we simplify the status change. The new item “Set status” in the user menu will allow you to set or clear the status without leaving the context. It also displays your current status with a message and Emodzhi - at the top, along with your name and nickname. 3r31240. 3r31233.  3r31251.

3r33336. 3r31240. 3r31233.  3r31251.

3r33333. Documentation on the status of 3r31239. and 3r33343. original ticket . 3r31240. 3r31233.  3r31251.

Includes additional files in 3r31198. .gitlab-ci.yml using r3r31198. include Now available in terms of Core

3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

We are happy to announce that starting from this release use include in 3r31198. .gitlab-ci.yml Moved from Starter to Core. Thus, templates and other shared resources will always be available for free and paid users, and everyone will have the opportunity to use this advanced development technology with reusable snippets for CI /CD pipelines. 3r31240. 3r31233.  3r31251.

3r33333. 3r31240. 3r31233.  3r31251.

Documentation for include and original ticket . 3r31240. 3r31233.  3r31251. 3r33381. Starting work 3r31198. only / except for changes to the file path or file 3r33535. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

We are pleased to present what you often asked for - the ability to use the rules 3r31198. only / except in 3r31198. .gitlab-ci.yml for work, if changes occur in a specific file or at the specified path. 3r31240. 3r31233.  3r31251.

This will give more control over repositories containing various resources and assemblies, since now only the necessary steps will be performed for new changes, which will speed up the work of the pipeline as a whole. 3r31240. 3r31233.  3r31251.

3r3408. 3r31240. 3r31233.  3r31251.

3r33434. Documentation on the use of restrictions in changes and 3r3415. original ticket . 3r31240. 3r31233.  3r31251. 3r33420. Added incremental scheduled deployment in Auto DevOps 3r33535. 3r31233.  3r31251.

(PREMIUM, ULTIMATE, SILVER, GOLD) 3r312340. 3r31233.  3r31251.

The ability to run incremental deployments in Auto DevOps has been available for some time, and with this release we add the ability to run deployments on schedule , so that it will be automatically conducted according to the specified schedule, if no errors occur. 3r31240. 3r31233.  3r31251.

3r33434. 3r31240. 3r31233.  3r31251.

3r33440. Scheduled incremental deployment document 3–3–31239. and 3r3442. original ticket . 3r31240. 3r31233.  3r31251.

Kubernetes RBAC support for applications running GitLab

3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

When setting up your infrastructure for the first time or connecting to an existing primary factor, security is a must. Role-based access control (RBAC) has become publicly accessible (GA) in Kubernetes 1.8 release, providing more precise control over access control to Kubernetes resources. 3r31240. 3r31233.  3r31251.

Our integration with Kubernetes now offers the ability to either create a cluster in the GKE (Google Kubernetes Engine) with RBAC connected, or connect to an existing cluster with RBAC, which will make your infrastructure safer. 3r31240. 3r31233.  3r31251.

3r33464. 3r31240. 3r31233.  3r31251.

3r33469. Documentation of clusters with RBAC and 3r33471. original ticket . 3r31240. 3r31233.  3r31251. 3r33476. RBAC support in Auto DevOps 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Auto DevOps now also supports application deployment on Kubernetes clusters with RBAC connected. 3r31240. 3r31233.  3r31251.

Role-based access control is an important tool that helps operators (deployment managers) ensure the reliability, security and efficiency of Kubernetes clusters. Using Auto DevOps in conjunction with a cluster with RBAC connected ensures that your applications get all the benefits of increased infrastructure security. 3r31240. 3r31233.  3r31251.

3r31240. 3r31233.  3r31251.

3r3809. Auto DevOps documentation and 3r?500. original ticket . 3r31240. 3r31233.  3r31251.

PostgreSQL database migration support and initialization for Auto DevOps 3r3-33535. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

We have improved the capabilities of Auto DevOps to automatically detect, build, test, deploy, and monitor your applications. Starting with release 11.? Auto DevOps provides the ability to initialize or migrate PostgreSQL databases into your project. 3r31240. 3r31233.  3r31251.

Simply set a project variable to initialize or migrate your PostgreSQL database, and Auto DevOps does the rest. 3r31240. 3r31233.  3r31251.

3r? 3522. 3r31240. 3r31233.  3r31251.

3r33535. Documentation for automatic deployment and 3r33529. original ticket . 3r31240. 3r31233.  3r31251. 3r? 3534. Other improvements in GitLab 11.4 are 3r33535. 3r31233.  3r31251. 3r33538. List of tags you follow 3r31173. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Labels in GitLab are very versatile, as they can be applied to tasks, merge-requests and epics. But the more tags you use, the harder it is to keep them in order. 3r31240. 3r31233.  3r31251.

In previous releases, we added a search for tags on the page with a list of project tags. Starting from this release, you can search for tags, sort them by name, creation date and change date, and view a list of tags that you are subscribed to. All this is available in the lists of group tags and tags associated with the project. 3r31240. 3r31233.  3r31251.

3r33555. 3r31240. 3r31233.  3r31251.

3r33560. Search documentation for tags and 3r?662. original ticket . 3r31240. 3r31233.  3r31251. 3r? 3567. Merge Requests Filtering by WIP 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Merge Requests are one of the main parts of GitLab. They allow project participants to work together on code while respecting transparency. We are in favor of the teams in the early stages sharing their work and using the WIP feature (“work in progress”, “in the process of development”), which shows that active work is still underway on the merge request, and it is too early to be inhibited. 3r31240. 3r31233.  3r31251.

In this release, we added a new filter for Merge Requests, which works both at the group level and at the project level, which helps users to more easily distinguish between WIP and non-WIP requests (“in work” and “ready”). This allows users to focus on merge requests, which are still in the early stages of work, unlike those that are closer to the final stages of testing before merge. 3r31240. 3r31233.  3r31251.

3r33584. 3r31240. 3r31233.  3r31251.

3r3-3589. WIP filter documentation and 3r???. original ticket . 3r31240. 3r31233.  3r31251. 3r? 3596. Allocation of personal references 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

In discussing a task or a merge-request with a large number of participants, it is difficult to see which comments are addressed to you. 3r31240. 3r31233.  3r31251.

Starting with this release, all mentions are on 3r31198. @ named the current user will be highlighted in a different color, which allows you to immediately see which comments are sent to you, and quickly focus on them. 3r31240. 3r31233.  3r31251.

3r3615. 3r31240. 3r31233.  3r31251.

3r3620. Documentation of references and 3r3622. original ticket . 3r31240. 3r31233.  3r31251.

Inserting GFM tables and links into Markdown by clicking 3r31173. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

GitLab supports GitLab Flavored Markdown (GFM) in most text input fields, expanding the formatting capabilities with a simple syntax. In particular, you can create tables on GFM. Previously, this function was difficult to use, especially when working with large tables, as you had to enter a lot of characters or insert the previous table in order to format it as you like. GFM also supports link management. But sometimes it is difficult to remember which syntax to use in this case. 3r31240. 3r31233.  3r31251.

Starting with this release, you can simply click on the button with the image of the table in the GFM editor, and the table will be inserted automatically. Then you can easily fill the cell values ​​of the table or extend it, setting it up as you like. This function can be used in descriptions and comments throughout GitLab. 3r31240. 3r31233.  3r31251.

Similarly, by clicking on the insert link button, you will get a template for the URL into which you can quickly insert the link address and its name. 3r31240. 3r31233.  3r31251.

Thanks George Tsiolis for the development of the insert table! 3r31240. 3r31233.  3r31251.

Thanks Jan Beckmann for developing a URL insert! 3r31240. 3r31233.  3r31251.

3r3660. 3r31240. 3r31233.  3r31251.

3r3665. Documentation for GFM and 3r3667. original ticket . 3r31240. 3r31233.  3r31251. 3r3673. Inclusion of new tasks in the work schedule 3r31173. 3r31233.  3r31251.

(STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD) 3r31240. 3r31233.  3r31251.

Burndown charts help teams keep track of progress in performing their work on malystone. Typically, the amount of work is discussed and approved before milestone begins. But sometimes this rule has important exceptions (such as an unexpected bug or a solution to a security problem), and you have to create new tickets for emerging tasks. 3r31240. 3r31233.  3r31251.

Starting from this release, work schedules will show information about new tasks that are created in the middle of Milestone, which is why there is a jump on the graph. 3r31240. 3r31233.  3r31251.

3r31240. 3r31233.  3r31251.

Expanded range of weights in the tasks API 3r31173. 3r31233.  3r31251.

(STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD) 3r31240. 3r31233.  3r31251.

Since the previous release, the values ​​of the weights of tasks can vary from zero to infinity (within reasonable limits). 3r31240. 3r31233.  3r31251.

In this release, we added the ability to set weights with a wider range using the task API. 3r31240. 3r31233.  3r31251.

3r337. Task API documentation 3r31239. and 3r33712. original ticket 3r31240. 3r31233.  3r31251. 3r33737. Quick blocking discussions 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Locking discussion of tasks and merge-requests helps to shift attention from old tasks and merge-requests to more urgent ones. You can also use this feature to prevent aggressive or unproductive behavior. 3r31240. 3r31233.  3r31251.

In this release, we added quick actions to lock and unlock discussions, so now you can block /unlock discussions along with posting a comment. 3r31240. 3r31233.  3r31251.

Thanks Mehdi Lahmam for this feature! 3r31240. 3r31233.  3r31251.

3r33737. 3r31240. 3r31233.  3r31251.

3r33737. Quick Action Documentation 3r31239. and 3r3747. original ticket . 3r31240. 3r31233.  3r31251. 3r3752. The closure of the epic 3r31233.  3r31251.

(ULTIMATE, GOLD) 3r31240. 3r31233.  3r31251.

This release adds the ability to close (and reopen) epics in GitLab, as well as tasks and merge requests. In the list of epics, there are now tabs Open (open), Closed (solved) and All (all), similar to the way it is implemented for tasks. So now, if you have completed all the work on the epic, or it is no longer relevant, it can be marked as completed (closed), and it will no longer appear in the list by default. 3r31240. 3r31233.  3r31251.

Now you can close and reopen the epic using the appropriate buttons or through quick actions, as well as through the API, as a task. 3r31240. 3r31233.  3r31251.

3r3769. 3r31240. 3r31233.  3r31251.

3r3774. Epic documentation and 3r3776. original ticket . 3r31240. 3r31233.  3r31251.

Improved admin settings panel

3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE) 3r312340. 3r31233.  3r31251.

Because of the large number of features that GitLab provides, administering GitLab can be quite a challenge. 3r31240. 3r31233.  3r31251.

In this release, we have made the admin settings panel more convenient to use. Now all the subsections of individual settings are on separate pages, which gives the administrator quick access to any settings that he needs to change. 3r31240. 3r31233.  3r31251.

3r31240. 3r31233.  3r31251.

Documentation on the admin settings panel 3r31239. and 3r3805. original ticket . 3r31240. 3r31233.  3r31251.

Sort projects by popularity

3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Our development team is doing everything possible to make it easier for you to search for relevant and interesting projects in your GitLab instance. In this release, a new filter “Most stars” has been added (sorted by the number of likes), which allows you to find projects with the highest number of marks in your instance. 3r31240. 3r31233.  3r31251.

Thanks Jacopo Beschi for this feature! 3r31240. 3r31233.  3r31251.

3r31240. 3r31233.  3r31251.

Project Search Documentation 3-3-31239. and 3r33636. original ticket . 3r31240. 3r31233.  3r31251. 3r33841. Displays the percentage of programming languages ​​used on the project page 3r31173. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Recently, we added language usage statistics to the project review page, which gives a general idea of ​​which programming languages ​​were used in development. 3r31240. 3r31233.  3r31251.

In GitLab 11.? we added a display of the percentage of code in each language. This allows you to get a quantitative description of the technology stack of your project. 3r31240. 3r31233.  3r31251.

Thanks 3r33858. Johann Hubert Sonntagbauer for this feature! 3r31240. 3r31233.  3r31251.

3r33838. 3r31240. 3r31233.  3r31251.

3r33869. Programming Language DocumentationI'm in the 3r31239 repository. and 3r33871. original ticket . 3r31240. 3r31233.  3r31251. 3r33876. Downloading two-factor recovery codes 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Actual two-factor authentication is a standard when logging into any modern web application. We, the developers of GitLab, understand this and take your security seriously. Every time you set up two-factor authentication, we provide a limited set of access recovery codes that allow you to regain access to your account in case of emergency. 3r31240. 3r31233.  3r31251.

Starting from this release, it is possible to download recovery codes as a text file using the “Download codes” button. 3r31240. 3r31233.  3r31251.

Thanks Luke Piccia for this feature! 3r31240. 3r31233.  3r31251.

3r33899. 3r31240. 3r31233.  3r31251.

3r3904. Recovery code documentation and 3r3906. original ticket . 3r31240. 3r31233.  3r31251. 3r33911. Filtering by type and status in the Runners viewer 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE) 3r312340. 3r31233.  3r31251.

The Runners viewing window now supports the ability to filter them by type and state, which gives more opportunities to manage large sets of Runners in the project environment. 3r31240. 3r31233.  3r31251.

3r33924. 3r31240. 3r31233.  3r31251.

3r33939. Runners documentation. and 3r33931. original ticket . 3r31240. 3r31233.  3r31251. 3r33936. Support for interactive web terminals has been added to the Docker artist. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE) 3r312340. 3r31233.  3r31251.

We expanded the functionality of interactive web terminals and made them compatible with Docker implementers. Currently, the Docker session ends as soon as the corresponding script ends, but we are working 3r3393945. over this problem 3r31239. and hope to solve it for the next release. 3r31240. 3r31233.  3r31251.

3r3951. 3r31240. 3r31233.  3r31251.

3r3r6956. Interactive Web Terminal Documentation 3r31239. and 3r3958. original ticket . 3r31240. 3r31233.  3r31251. 3r3393963. Skipping Auto DevOps jobs when functions are unavailable 3r31173. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Starting with version 11.? Auto DevOps will evaluate the plan (when hosting on GitLab.com) or the profile (when self-hosting) for the instance in which it is running to determine which work to skip. As a result, the Auto DevOps pipeline will run faster as unused functions will be skipped. 3r31240. 3r31233.  3r31251.

This will allow you to save time, and now your pipeline schedule will look neater, since only relevant work for your project will be marked on it. 3r31240. 3r31233.  3r31251.

3r3809. Auto DevOps documentation and 3r33982. original ticket . 3r31240. 3r31233.  3r31251. 3r33987. Conveyors can set the execution of work on a schedule 3r31173. 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

The new release has the opportunity to postpone the start of work through the keyword ключевое when ’in the file gitlab-ci.yml . The countdown starts from the moment when the work should start to be performed taking into account the delay, which gives you the opportunity to add work that should be performed after a certain period of time - for example, when using incremental deployment or in other cases where further actions should be performed after the delay. 3r31240. 3r31233.  3r31251.

3r31240. 3r31233.  3r31251.

Documentation on the postponement of work 3r31239. and original ticket . 3r31240. 3r31233.  3r31251.

Interactive task lists with Nurtch and JupyterHub

3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Interactive task lists (runbooks) provide operators with an excellent opportunity to interact with various systems to perform diagnostics, deployment and evaluation of infrastructure components. 3r31240. 3r31233.  3r31251.

JupyterHub, an application made available by integrating GitLab and Kubernetes, now includes the Nurtch library. Rubix , which makes it possible to create task lists for DevOps. As an example, a test list of tasks is presented, demonstrating 3r31029. basic operations 3r31239. . 3r31240. 3r31233.  3r31251.

3r31240. 3r31233.  3r31251.

3r31040. Installation documentation for the application 3r31239. and 3r31042. original ticket

. 3r31240. 3r31233.  3r31251. 3r31047. Added manual entry when filling out the lists of licenses 3r31173. 3r31233.  3r31251.

(ULTIMATE, GOLD) 3r31240. 3r31233.  3r31251.

The license management policy allows developers to confirm the use of individual licenses in a project, or to blacklist them. This can be done directly on the merge-request page as soon as a new license appears. But sometimes Maintainers want to make a list of licenses in advance so that developers know if the changes they make are consistent with the project's policy. 3r31240. 3r31233.  3r31251.

In GitLab 11.? we added the ability to manually enter when compiling a list of licenses. Maintainers can fill out the list on page 3—3–31060. Settings> CI /CD> License Management , choosing licenses from the standard set or adding them manually. 3r31240. 3r31233.  3r31251.

3r31066. 3r31240. 3r31233.  3r31251.

3r31071. Documentation for manually filling in license lists 3-33-3399. and 3r31073. original ticket . 3r31240. 3r31233.  3r31251. 3r31078. The metrics panel now displays thresholds for alerts 3r31233.  3r31251.

(ULTIMATE, GOLD) 3r31240. 3r31233.  3r31251.

Starting from GitLab 11.? the specified alert thresholds are displayed directly on the metric graphs. This makes it easier to determine which metrics generate alerts at the moment, and also allows you to get a visual representation of the interaction between metrics and alert thresholds. 3r31240. 3r31233.  3r31251.

3r31091. 3r31240. 3r31233.  3r31251.

3r31096. Alert threshold documentation for r3r31239. and 3r31098. original ticket . 3r31240. 3r31233.  3r31251.

Git v2 protocol

3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)

3r31233.  3r31251.

Developers update local repositories ( Git fetch ) Several times a day to check if the current branch is lagging behind the latest version of the repository branch. The Git v2 protocol is an important update to data transfer protocol 3r31239. which is responsible for the exchange of data between the client (your computer) and the server (GitLab) during cloning, retrieval and pushing. The new data transfer protocol improves the performance of fetches and makes it possible to further improve the protocol. 3r31240. 3r31233.  3r31251.

Previously, when invoking fetch commands, a list of all links in the repository was displayed. For example, if you update for one branch (3r31198. Git fetch origin master 3r31199.), Then you will also see a full list of all links. When it comes to a big project, you can get more than 10?000 links and dozens of megabytes of data. 3r31240. 3r31233.  3r31251.

Git v2 protocol has been supported since Git v???.? but is not used by default. To activate it, call the command 3r31198. git config --global protocol.version 2 . On GitLab.com, the Git v2 protocol is not yet connected by default when working over SSH. If you want to use it, you need to connect it manually. 3r31240. 3r31233.  3r31251.

3r31132. Git v2 protocol configuration documentation and 3r31134. original ticket . 3r31240. 3r31233.  3r31251. 3r31139. Improved UX admin settings panel Geo 3r31233.  3r31251.

(PREMIUM, ULTIMATE) 3r31240. 3r31233.  3r31251.

For a Geo administrator, it is critical to monitor the loading and synchronization of secondary nodes when working with geographically distributed commands. 3r31233.  3r31251. In GitLab 11.? we improved UX Geo on the admin panel, adding even more synchronization and verification information to the user interface. When you click the “Open projects” button in the profile on the primary node, a link is generated to the list of projects on the corresponding secondary node. The profiles on secondary nodes in the new “All” tab contain basic information on the verification status of all projects. 3r31240. 3r31233.  3r31251.

We have plans further improvements to the UX 3r31239. ! 3r31240. 3r31233.  3r31251.

3r31160. 3r31240. 3r31233.  3r31251.

3r31165. UX Geo documentation. and 3r31167. original ticket . 3r31240. 3r31233.  3r31251. 3r31172. Prometheus 2.0 update for Omnibus GitLab 3r31233.  3r31251.

(CORE, STARTER, PREMIUM, ULTIMATE) 3r312340. 3r31233.  3r31251.

Omnibus Gitlab comes with Prometheus, which gives 3r31181. a visual representation of the deployed instances . The Prometheus development team has released a major update in the form of a new 2.x series, which includes 3r31183. improvements. among which are improved performance and a more convenient time series database format. Unfortunately, the change in the database architecture has led to the fact that it does not support backward compatibility with the old format of the 1.x series. 3r31240. 3r31233.  3r31251.

Starting with GitLab 11.? Prometheus ??? is included in the Omnibus package, so you can already take advantage of it. 3r31240. 3r31233.  3r31251. 3r31192.  3r31251.

Versions 11.4 and higher will work with Prometheus 2 3r3-31207.  3r31251. Already installed versions will not be updated automatically. We have added a new team 3r31198. gitlab-ctl prometheus-upgrade for 3r31219. update prometheus and migrate the necessary data 3r3r1239. . Prometheus will be suspended for the duration of the data transfer.
 3r31251.
Version GitLab ???r3r31205. will automatically upgrade to Prometheus ???r3r31239. . However, Prometheus 1.0 data will not be automatically transferred.
 3r31251.
3r31233.  3r31251.
For more information on updating Prometheus to 2.4.? please refer to our 3r31219. documentation updates for 3r31239. . 3r31240. 3r31233.  3r31251.
3r31219. Documentation of updates 3r31239. and 3r31221. original ticket
. 3r31240. 3r31233.  3r31251. 3r31226. 3r31233.  3r31251.
Detailed release notes and instructions for updating /installing can be found in the original English post: 3r31230. GitLab 11.4 released with Merge Request Reviews and Feature Flags
. 3r31240. 3r31233.  3r31251.
Worked on the translation from English cattidourden , 3r31238. rishavant
and @maryartkey. 3r31240. 3r31247. 3r31251. 3r31251. 3r31244. ! function (e) {function t (t, n) {if (! (n in e)) {for (var r, a = e.document, i = a.scripts, o = i.length; o-- ;) if (-1! == i[o].src.indexOf (t)) {r = i[o]; break} if (! r) {r = a.createElement ("script"), r.type = "text /jаvascript", r.async =! ? r.defer =! ? r.src = t, r.charset = "UTF-8"; var d = function () {var e = a.getElementsByTagName ("script")[0]; e.parentNode.insertBefore (r, e)}; "[object Opera]" == e.opera? a.addEventListener? a.addEventListener ("DOMContentLoaded", d,! 1): e.attachEvent ("onload", d ): d ()}}} t ("//mediator.mail.ru/script/2820404/"""_mediator") () (); 3r31245. 3r31251. 3r31247. 3r31251. 3r31251. 3r31251. 3r31251.
+ 0 -

Add comment