GitLab 11.5 is released with control panels for operators and security professionals and access control for GitLab Pag

 3r31515. 3r3-31. 3r31494. GitLab 11.5 is released with control panels for operators and security professionals and access control for GitLab Pag 3r? 31503. 3r31492.  3r31515.
Security control panel within the group
3r31492.  3r31515. 3r31494. Developers have long been using GitLab as a tool to secure their code. GitLab now gives security professionals more empowerment so they can use it to improve application security and ensure compatibility. With the release of 11.? the new 3r312. group security panel 3r331502. Collects all the information that security professionals may need in a convenient way designed specifically for them. This panel contains new display options: an overview of the security information of various projects, as well as in-depth information about each of them. At 11.5 we start with SAST reports, in future releases we will add new reports to this panel. Our goal is to create a handy tool, a single security panel that security experts can use instead of switching between multiple tools. 3r? 31503. Control access to Pages requested especially often, and as a result, This feature was added by the members of the 3-3331502 community themselves. . 3r? 31503. 3r31492.  3r31515.
Knative for Kubernetes
3r31492.  3r31515. 3r31494. Serverless (“serverless”) application architecture is now much discussed, but often misunderstood. Some believe that serverless computing implies "Function as a Service" (FaaS), but this is 3r-358. not quite right
. In short, serverless architecture allows you to focus on writing business logic, without requiring an understanding of the underlying infrastructure on which your software will run. Thus, applications and functions can be serverless. 3r? 31503. 3r31492.  3r31515. 3r31494. Knative - This is a Kubernetes platform designed to create, deploy and manage modern serverless projects, and in GitLab 11.5 we added the ability to 3r366. Easily deploy and integrate Knative with GitLab
. You can install Knative on the connected cluster Kubernetes one action. In GitLab 11.5 you can use Knative for your serverless applications, support serverless functions will be added in 11.6. 3r? 31503. 3r31492.  3r31515. 3r31494. Currently, Knative is still in alpha, but there are many good reasons to deploy applications with it, as it comes with powerful features right out of the box. For example, Knative monitors the loading of the hearth and can automatically increase or decrease their number without additional configuration. Knative also has event handling, which makes it easier to manage communications between Producer and Consumer services when deploying microservices. 3r? 31503. 3r31492.  3r31515.
And even more! 3r33357. 3r31492.  3r31515. 3r31494. There are so many cool innovations in this release that we couldn't fit all of them into the intro. Further features such as await you. attribute parallel for conveyor , 3r388. redesign cards on the task board and the initial 3r390. integration with Jaeger . In this release, we have made significant improvements to the code review process, making it easier and more convenient: for example, added the possibility of 3r3392. comment unchanged code lines in merge-request , 3r3394. Preview of a merge request before sending it 3r3-31502. , automatic the appointment of code owners confirming merzh-request 3r3-31502. and 3r3398. Direct links to review applications (Review Apps) 3-3331502. . Read on, and you will learn about all the new features that are included in this release. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3104. We invite you to our meetings 3r3-31502. . 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31-10. 3r? 31503. 3r31492.  3r31515. 3r3114. 3r3115. MVP this month - Tuomo Ala-Vannesluoma 3r33357. 3r31492.  3r31515. 3r31494. Tuomo did a great job by implementing 3r3123. access control to GitLab Pages - a popular feature that many have asked to add. Private projects can now restrict access to their content, which allows you to create and store internal pages with private information. 3r? 31503. 3r31492.  3r31515. 3r31494. Thank you, Tuomo! This contribution required significant work in projects 3r3129. gitlab-ce 3r? 31502. , 3r3133. gitlab-pages 3r? 31502. and 3r3r137. omnibus-gitlab 3r? 31502. . 3r? 31503. 3r31492.  3r31515. 3r3144. The main features of the release of GitLab ???r3333357. 3r31492.  3r31515. 3r3148. Security control panel within the group 3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. Security professionals need to easily obtain information on the current security status of all their projects in order to know which task will be the most important now. This is even more important for security directors who need to review potential critical vulnerabilities affecting the entire development. 3r? 31503. 3r31492.  3r31515. 3r31494. In the release of GitLab 11.? we present the first version of the new security control panel available at the group level. She collects in one place. SAST vulnerabilities for all projects of this group and a list of available actions to fix them. For example, you can create a task with the proposed solution, or just hide the notification if you think that this is an erroneous response. Future releases will add support for other tests - Dependency Scanning, Container Scanning, DAST. 3r? 31503. 3r31492.  3r31515. 3r31494. Please note That the group security panel requires the use of the new syntax for reports 3r3605. reports 3r? 31502. and GitLab Runner version 11.5 or higher for displaying results. Support Auto DevOps will be added in the next release. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3179. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3184. New dashboard documentation. and 3r3186. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3191. Control panel for operators 3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. For companies and teams using DevOps, it is important to be able to quickly access information about the status of projects. 3r? 31503. 3r31492.  3r31515. 3r31494. Release 11.5 presents a new panel for operators, containing an overview of all important metrics for projects to which the user is subscribed, for example, the time since the last deployment, the last commit and active alerts. 3r? 31503. 3r31492.  3r31515. 3r31494. This panel can be configured as a home page for the user, or it can be accessed by clicking on the icon in the top panel. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. Documentation on the new panel for operators and original ticket . 3r? 31503. 3r31492.  3r31515.

Controlling access to GitLab Pages

3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE) 3r3-31503. 3r31492.  3r31515. 3r31494. In the release of GitLab 11.? we present an amazing feature introduced by the community - access control to GitLab Pages. Previously, we supported only those cases in which all the content on the project was public, but now using Pages you can create and publish protected content, access to which will be open only to project participants. Operations documents, secret data, plans and other information can now be published confidentially, providing access to it for a limited number of people. 3r? 31503. 3r31492.  3r31515. 3r31494. So far, this feature is not connected to GitLab.com, more information in ticket 5576 . 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. Documents access control documentation for Pages and original ticket . 3r? 31503. 3r31492.  3r31515.

Deploying and integrating Knative with GitLab

3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. Creating serverless applications gives teams the opportunity to focus on creating a quality product, eliminating the need to configure and maintain servers. 3r? 31503. 3r31492.  3r31515. 3r31494. Starting with the release of GitLab 11.? it is possible to deploy Knative to your Kubernetes cluster in a single action, using GitLab integration with Kubernetes. Knative - Kubernetes platform designed to create, deploy and manage modern serverless projects. Previously complex tasks, such as assembling from source to container, traffic management and scaling to 0 (scaling-to-zero) with no load, now work right out of the box. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. Documentation for serverless architecture in GitLab 3r3-31502. and original ticket . 3r? 31503. 3r31492.  3r31515.

The appointment of the owners of the code confirming merzh-request

3r31492.  3r31515. 3r31494. (STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. It is not always obvious who should conduct a merge-request review. Code owners, who are designated to be responsible for specific files, are now automatically assigned as confirming a merge request. 3r? 31503. 3r31492.  3r31515. 3r31494. With the automatic assignment of confirming merge-requesters, the code owners will be notified of the changes, so that they can review them and approve or not miss the changes. 3r? 31503. 3r31492.  3r31515. 3r31494. Support for the owners of the code appeared in the release of GitLab 11.3 (3r3305. The original article 3-3331502., 3r3-3307. Translation 3-3331502.). In future releases, the degree of participation of code owners in merger-request workflows will increase from 3-33309. required proof of ownership . 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33333. 3r? 31503. 3r31492.  3r31515. 3r31494. Documentation for confirming merzh-request 3r3-31502. and 3r3322. original ticket . 3r? 31503. 3r31492.  3r31515.

Attribute parallel to speed up work with conveyor

3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. The speed of the pipeline is an important factor for any team, and performing tests or other tasks that can be parallelized usually takes a lot of time for any assembly. Add new keyword attribute 3r31390. parallel - allows teams to easily parallelize tests, speeding up the software delivery process. To use this feature, set the attribute the number of threads in which you want to run this task, and GitLab will create the necessary amount of work for your task on its own. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. Documentation on the parallel attribute and 3r33351. original ticket . 3r? 31503. 3r31492.  3r31515.

Other improvements in GitLab ???r3r3357. 3r31492.  3r31515. 3r33360. Commenting on unmodified lines of code in a merge request 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. One of the key objectives of code review is to draw attention to aspects of the proposed changes that may not yet have been considered. Often these are indications of unintended consequences that may arise in unmodified code. 3r? 31503. 3r31492.  3r31515. 3r31494. GitLab now supports commenting on both modified and unaltered lines of code in a merge request, so you can draw the author’s attention to changes that need to be made. To display unchanged lines of code when reviewing changes to a merge request, press the button with ellipsis (3r3-301018. 3r3-31019.). 3r? 31503. 3r31492.  3r31515. 3r31494. In future releases, we will expand commenting support for 3r33379. unchanged files . 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33385. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33333. Documentation for discussions in merge requests 3-3-331502. and original ticket . 3r? 31503. 3r31492.  3r31515.

File templates for group

3r31492.  3r31515. 3r31494. (PREMIUM, ULTIMATE, SILVER, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. File Templates 3r31390. LICENSE , .gitignore , Dockerfile , and 3r31390. .gitlab-ci.yml make it easy to add these frequently used files to projects. Custom shaFile blonds can now be shared among all projects in a group and in subgroups if you configure a group template repository. 3r? 31503. 3r31492.  3r31515. 3r31494. Custom templates are useful in cases where GitLab templates are not suitable: for example, when you need your own license, which is used in all projects of the company, or a complex Dockerfile, which should be used in each microservice. 3r? 31503. 3r31492.  3r31515. 3r31494. Template file support for user instances was introduced in the release of GitLab 11.3 (3r3-33422. Original article 3r?33?502., Translation 3r31502.). 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33430. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33434. File template documentation for the group 3r3-31502. and 3r3437. original ticket . 3r? 31503. 3r31492.  3r31515.

Direct link to apps for review 3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. When you work in a separate branch and change only a few files, you do not need a link to the review applications to take you to the root of the project. For convenience, we added a drop-down menu to the link to the review applications, which now allows you to navigate directly to the pages of the files you worked with. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33460. Documentation on the direct transition from source files to their pages in the environment 3r3-31502. and 3r33462. original ticket . 3r? 31503. 3r31492.  3r31515.

Task Analytics 3r31443. 3r31492.  3r31515. 3r31494. (PREMIUM, ULTIMATE, SILVER, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. In this release, we presented a dynamic diagram showing the number of tasks created in your group per month or in the past year. We also added a filter that allows you to narrow the search to a specific set of tasks. 3r? 31503. 3r31492.  3r31515. 3r31494. This feature will help teams conduct a deeper analysis of tasks. For example, you can quickly see how many tasks for the bugs were created if you select the appropriate “bug” mark. 3r? 31503. 3r31492.  3r31515. 3r31494. Here you can see how we are planning Extend chart capabilities 3r3-31502. . We ask you to participate in the discussion! 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33490. 3r? 31503. 3r31492.  3r31515. 3r31494. Task Analytics Documentation 3-3331502. and 3r3497. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3502. Preview of a merge request before departure 3r3r1443. 3r31492.  3r31515. 3r31494. (PREMIUM, ULTIMATE, SILVER, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. Code review is a must-have practice in any successful project, but sometimes it is difficult to provide a clear and executable feedback. One of the problems is that the comments on the code become irrelevant or incomplete as the reader understands what changes have been made by looking at the diff. 3r? 31503. 3r31492.  3r31515. 3r31494. In GitLab 11.? we presented a feature for the Merge Requests Review, which allows you to write and send several feedback items in one action. Starting with this release, you can view reviews of your Merge-Requests before sending them. 3r? 31503. 3r31492.  3r31515. 3r31494. In the next versions we will improve this feature by adding 3r33519. email notifications - one for each review of a merge request. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33525. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33535. Documentation for previewing merge-requisitions review 3r3-331502. and 3r33232. original ticket . 3r? 31503. 3r31492.  3r31515. 3r33537. Keep your email secretly

3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. When collaborating on a project, it is important to know who exactly is making changes to the code, and to be able to view the author’s profile through the GitLab interface with local use or on a host located remotely, but this puts your email on a public display. 3r? 31503. 3r31492.  3r31515. 3r31494. GitLab now provides noreply an address that can be used locally or for web commits to make it easier for you to keep your email secret. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33556. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33561. Documentation for private email and 3r36363. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3-3568. New CI /CD syntax for safety, quality and performance reports 3r31443. 3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. Prior to GitLab 11.? reports such as SAST or DAST relied on a combination of task names and artifacts so that the system could recognize their type. Because of the increased performance requirements for accessing artifacts, such functionality was difficult to scale and support more advanced features like Group Security Dashboard. With the previous syntax, you always had to give the work certain names (for example, 3r3131390. Sast ), But now you can specify any name you like for each work. 3r? 31503. 3r31492.  3r31515. 3r31494. In GitLab 11.? a new feature was introduced to use the new syntax 3r31390. reports for reports. Documentation on the creation of works with the new syntax is available at the links: 3r-3585. SAST , 3r33587. DAST , 3r???. Determination of dependencies 3r3-31502. , 3r???. Scan container , 3r33593. License management , 3r33595. Evaluation of the quality of the code and 3r33597. Performance testing in the browser . 3r3599. The old syntax is 3r3-31502. gone into the background, and in a future release, we may get rid of it. We’ll be happy if you update your work to take advantage of the improved performance and security panel of the group, even though the old syntax still works. To use the new syntax, GitLab Runner 11.5 or higher is required. 3r? 31503. 3r31492.  3r31515. 3r31494. Reporting documentation 3-3331502. and 3r3607. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3612. Opening a merge-request with a patch via email 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. GitLab has long supported the opening of Merge Requests via email, but earlier, before sending email, the branch should have already been created on the server. Now you can open merge-requests using one email, attaching one or more patch files to the letter (3r31390. .Patch ). 3r? 31503. 3r31492.  3r31515. 3r31494. Patch files are a standard for sharing and transferring changes between systems. In future GitLab releases, we will create 3r3627 based on them. distributed merge requests 3r3-31502. which will allow you to share merge-requests between GitLab instances and other tools for hosting Git. 3r? 31503. 3r31492.  3r31515. 3r33232. 3r33333. 3r3634. 3r33535. 3r31511. 3r31511. 3r31511. 3r31492.  3r31515. 3r31494. Documentation on the opening of merge-requests via email 3r3-31502. and 3r34545. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3650. Empty homepage on wiki projects 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. We have improved the wiki project creation process by removing the default project viewing page. Now the default home page is empty, which inspires users to add their own pages to the corresponding wiki and further development of projects. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3663. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3668. Wiki Project Documentation 3r3-31502. and 3r3670. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3675. Opening Jaeger via GItLab 3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. Tracing provides an in-depth analysis of the performance and integrity of the application being deployed, since it can be used to track every function and microservice that processes this request. This makes it easier to process the request from start to finish, regardless of whether you are using a monolithic or distributed system. 3r? 31503. 3r31492.  3r31515. 3r31494. In GitLab 11.? we included the initial integration with 3r33688. Jaeger , 3r3690. the CNCF project. tracing, which allows users to easily open the Jaeger user interface from GitLab. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. Trace documentation and original ticket . 3r? 31503. 3r31492.  3r31515.

Consistent names of task status checks when integrated with GitHub

3r31492.  3r31515. 3r31494. (PREMIUM, ULTIMATE, SILVER, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. Now it became possible to set the status checks of tasks on the GitHub side, simply by ticking “required”, without having to set up checks for each task individually based on their name. Previously, the names of the checks included the name of the branch, so the check could not be done simply. This feature can be connected in the settings section of the integration with GitHub. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33737. 3r? 31503. 3r31492.  3r31515. 3r31494. Documentation on the status check titles 3r3-31502. and original ticket . 3r? 31503. 3r31492.  3r31515. 3r33337. Omnibus Go apps now use the GitLab certificate directory. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE) 3r3-31503. 3r31492.  3r31515. 3r31494. GitLab includes a range of Go-based applications. Prior to version 11.? these applications used the standard system directory for trusted certificates instead of the Omnibus GitLab directory. 3r? 31503. 3r31492.  3r31515. 3r31494. Starting from this release, Go applications use the same directory for trusted certificates as the rest of GitLab. The default is /opt /gitlab /embedded /ssl /certs / . Using a common directory makes managing certificates easier and allows you to work with them directly. 3r? 31503. 3r31492.  3r31515. 3r31494. If you have GitLab installations that have dependencies related to the fact that Go applications used the system directory, move these certificates to the standard Omnibus GitLab directory. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3756. Documentation for installing certificates and 3r3758. original ticket . 3r? 31503. 3r31492.  3r31515.

Notice of closing epic 3r3r4343. 3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. Recently, we have added the ability to close epics, namely, to set different states of epics: open and closed. In this release, we also added notifications about the closure of epic or re-opening them, to make it easier for users to track changes in projects that interest them. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. Notification documentation 3-3331502. and 3r3783. original ticket . 3r? 31503. 3r31492.  3r31515. 3r33788. Logging audit events in JSON

3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE) 3r3-31503. 3r31492.  3r31515. 3r31494. To simplify the analysis of audit events and their use outside of GitLab, we added the file audit_json.log , for recording audit-events in a structured log file. With this innovation, sending and parsing logs will be much easier, especially for visualization and analysis using other tools. 3r? 31503. 3r31492.  3r31515. 3r31494. Audit event documentation 3r3-31502. and 3r3805. original ticket . 3r? 31503. 3r31492.  3r31515.

Auto-complete function for epics in the description of tasks and merge-requests

3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. Now it’s even easier to search for epics and link to them when working on a task or a merge request. Just enter & and a few numbers or symbols in the description of the task or merge-request or in the comment. Using GitLab's autocomplete feature, the epic will be searched directly in the parent group, which allows you to select one of them without leaving the current page. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33825. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33838. Documentation for special links GitLab 3r3-31502. and 3r33232. original ticket . 3r? 31503. 3r31492.  3r31515. 3r33837. List of files for viewing changes in merge-request 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. When viewing merge requests, you almost always have to move back and forth between files. Now, in addition to the file tree added to GitLab 11.4 (3-333846. The original article 3-3331502., 3r3-3848. Translation 3r3-331502.), GitLab includes a list of files with changes that can be searched, making it easier to see which files have changed, and switch between them through a list or a tree - whatever you like. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33854. 3r31492.  3r31515. 3r31494. 3r33859. Documentation for navigating changed files 3r3-31502. and 3r33861. original ticket . 3r? 31503. 3r31492.  3r31515. 3r33866. More information about deployment in Merge Requests 3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. At the moment, information about the environment is hidden when starting a new pipeline. In this release, we add output information about the deployments to the widget to let you know that an update is currently taking place. 3r? 31503. 3r31492.  3r31515. 3r31494. One of the most interesting results that can be obtained using this feature is that the link to the current deployment will remain available in cases when a new deployment is already running, which will allow you to find a link to the application page for the review. Previously, it was quite difficult to choose the right moment, in cases where multiple deployments occur simultaneously. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3883. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3888. Documentation on the status of the pipeline in Merge Requests 3r3-331502. and 3r33890. original ticket . 3r? 31503. 3r31492.  3r31515. 3r39595. Authentication in Jira Cloud via email or API 3r31443 token. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. Jira Cloud is going to get rid of usernames when authenticating r3r31502. . To support this change, we will now allow you to use an email address or API token instead of a username to authenticate with the Jira Cloud. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33915. Documentation for integrating Jira with GitLab 3r3-31502. and 3r33917. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3393922. Automatic transition to the last visited task board 3r31443. 3r31492.  3r31515. 3r31494. (STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. As soon as teams begin to use many task boards, it becomes inconvenient to move from one task to another using drop-down lists. With this release of GitLab, you automatically get to the last visited board when navigating task boards from the side menu of a project or group. This information is stored in the system, so even if you use GitLab in several browsers and on different devices, you will see the last visited board. 3r? 31503. 3r31492.  3r31515. 3r31494. Note that you can still link to a specific board using a direct URL that you can save when viewing it. 3r? 31503. 3r31492.  3r31515. 3r31494. You can view and discuss future planned improvements in 3r33939. managing multiple boards . 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3393945. Documentation of multiple task boards 3r3-331502. and 3r33947. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3952. Filter by open or closed epics in API 3r31443. 3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. Recently, we have added the ability to close epics, namely, to set different states of epics: open and closed. In release 11.? we make these states available in the API itself so that you can get a list of open or closed epics, filtering by state, and also see the state of a single epic. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33965. API documentation epic 3r3-31502. and 3r33967. original ticket . 3r? 31503. 3r31492.  3r31515. 3r33939. Milestone Change Notification 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. The GitLab mails are useful for teams to plan and track work done during a certain period of time, as well as to communicate with releases. These dates are important for teams to coordinate the work schedules of all interested parties. Therefore, it is imperative that everyone knows when the Milestone dates change. 3r? 31503. 3r31492.  3r31515. 3r31494. In this release, we added email notifications about changing milestones in tickets and merge requests so that people can stay up to date if some of the work was postponed to a later or early date or simply postponed. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r33989. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r3994. Notification documentation 3-3331502. and 3r3996. original ticket . 3r? 31503. 3r31492.  3r31515.

Keyboard shortcuts for epic

3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. You can perform basic operations on the epic page (just like on ticket and merge-requesting pages) using keyboard shortcuts, which is convenient for those users who prefer to do more and faster without leaving the keyboard. 3r? 31503. 3r31492.  3r31515. 3r31494. Click r to start writing a new comment, with the selected text quoted. Use e to edit the description, l to change tags. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31024. Keyboard documentation 3r3-31502. and 3r31026. original ticket . 3r? 31503. 3r31492.  3r31515. 3r3-1031. Change the design of the cards on the task board 3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. The central place to work together in GitLab is the Issue Boards, where teams can organize and view planned and current work in one place. In this release, we have improved the design of ticket cards, now they display only the necessary information in a simple and organized manner. The card displays only the name of the ticket, time accounting information, confidentiality, tags, the estimated end date, weight and responsible for the ticket. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31044. 3r? 31503. 3r31492.  3r31515. 3r31494. Task board documentation 3r3-31502. and 3r3-1051. original ticket . 3r? 31503. 3r31492.  3r31515.

Displaying the 'index' files in the repository is the same as the 'README'

3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. When in the repository directory there is a file README. * , it automatically “renders” GitLab without the obvious need to open it. With GitLab 11.5 you can now do the same with the file. index. * 3r31391. (in the absence of 3r31390. README. * ). 3r? 31503. 3r31492.  3r31515. 3r31494. This is especially useful when you also deploy your content on the Internet using a static site generator. Previously, if you used README.md , it would produce a file named README.html , whereas with index.html “more elegant” URLs can be obtained, since most web servers count 3r31390 addresses. http://example.com/page/index.html and 3r31390. http://example.com/page/ the same 3r? 31503. 3r31492.  3r31515. 3r31494. This feature applies not only to Markdown files, since GitLab supports several 3r31089. markup languages ​​ . 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31095. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31100. Documentation for the automatic visualization of files README. 3r31101. and index. 3r31-102. 3r? 31502. and 3r31-1010. original ticket . 3r? 31503. 3r31492.  3r31515.

RBAC creates a service account limited to the project namespace 3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD) 3r31492.  3r31515. 3r31494. Security of Kubernetes instances is of paramount importance for running ready-to-production important applications. RBAC (Role-based access control, role-based access control) provides greater power and flexibility in securing your cluster. 3r? 31503. 3r31492.  3r31515. 3r31494. Starting from GitLab 11.? our integration of Kubernetes will create a dedicated service account and role binding for the namespace of each project that (both the record and the binding) will be used in the CI GitLab works. Thus, the token cluster-admin when interacting with GitLab, CI Runners will not be needed. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r?13?128. Documentation for RBAC 3r3-31502. and 3r31130. original ticket
. 3r? 31503. 3r31492.  3r31515. 3r31135. Discussion activity filter in tickets and merge requests 3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. We are glad to see that the teams actively cooperate in comments to tickets and merge-requests. For active discussions and long-lived tickets and merge-requests, the discussion can be very large, with a lot of generated system messages. 3r? 31503. 3r31492.  3r31515. 3r31494. In this release, we have implemented a filter that allows you to focus only on comments or only system messages in the area of ​​discussion of the ticket or merge-request. Your selection is saved for all tickets and for all merge requests in GitLab. Therefore, if you prefer any one mode, you can make a choice once and for all. 3r? 31503. 3r31492.  3r31515. 3r31494. We are planning to add same functionality for epic 3r3-31502. . 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31158. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31232. Discussion documentation 3-3331502. and 3r31165. original ticket . 3r? 31503. 3r31492.  3r31515. 3r31170. Updating Git submodules via API
3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. Git submodules allow you to include a Git repository in another Git repository. GitLab now supports updating the submodule link via the API. This feature is especially useful for automation, as it allows using the API to update the project to use the latest dependencies. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31183. Documentation on the use of submodules 3r3-31502. and 3r31185. original ticket
. 3r? 31503. 3r31492.  3r31515. 3r31190. Show feedback if Git push checking takes too long
3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. Each time you submit changes to the Git repository on GitLab, GitLab checks each commit for access rights and repository size limits, and also checks for the presence of LFS objects (Large File Storage). Sometimes large pushes can silently end in failure if verification takes too long. 3r? 31503. 3r31492.  3r31515. 3r31494. Now GitLab provides feedback if the push fails due to too long a check. This feature is useful for finding the source of a problem. 3r? 31503. 3r31492.  3r31515. 3r31494. Timeout documentation for git push /pull and original ticket . 3r? 31503. 3r31492.  3r31515. 3r31214. Redesign Ticketing, Merge Requests and Epic 3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. In this release, we have improved the design of discussions in tickets, merge requests and epics. It is now easier to read comments and analyze system messages, so that you can focus on relevant and relevant information. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31227. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31232. Discussion documentation 3-3331502. and 3r31234. original ticket
. 3r? 31503. 3r31492.  3r31515. 3r31239. Quick access to the priority settings of the group 3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. With GitLab 11.? we consistently improve the group settings page to facilitate access to the most requested configuration options. By default, the topmost part of the settings is shown in expanded form, and we also refined the tags and links to make it clear where to find the settings and what they do. We continue to work on this: the project and admin settings pages will improve soon! 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31252. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31282. Group Documentation 3r3-31502. and 3r31259. original ticket
. 3r? 31503. 3r31492.  3r31515. 3r31264. Redesign of the new group creation page 3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. In this release, we make the New Group page (‘New group’) look like the New Project страницу page, combining and rearranging the relevant fields to make the pages more understandable and consistent with each other. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31277. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31282. Group Documentation 3r3-31502. and 3r31284. original ticket
. 3r? 31503. 3r31492.  3r31515. 3r31289. Help menu in the top navigation
3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. In this release, we update the top navigation bar by moving two menu items to the new highlighted Help section. Soon we will add additional help menu items related to your instance and feedback! 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. The original ticket . 3r? 31503. 3r31492.  3r31515. 3r31312. Correction Tips by Gemnasium
3r31492.  3r31515. 3r31494. (ULTIMATE, GOLD) 3r3-31503. 3r31492.  3r31515. 3r31494. 3r31338. Dependency Scanning 3r3-31502. Works on the basis of 3r3-331323. the Gemnasium service
for most supported languages. Because of this, GitLab reports known vulnerabilities in packages, but this information does not provide a fix method that would help developers easily fix the problem. 3r? 31503. 3r31492.  3r31515. 3r31494. With GitLab 11.? Gemnasium offers fixes whenever possible. This is reported in the vulnerability information window and in the corresponding ticket. For example, a fix may report a minimum version to which the library needs to be updated in order to fix a security issue. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31338. Documentation for scanning dependencies 3r3-31502. and 3r31340. original ticket
. 3r? 31503. 3r31492.  3r31515.
Logging audit events for project functions and group settings 3r31443. 3r31492.  3r31515. 3r31494. (PREMIUM, ULTIMATE) 3r3-31503. 3r31492.  3r31515. 3r31494. Audit events mark important events that occur on your GitLab instance, and now we record additional changes at 11.5:
3r31492.  3r31515. 3r31458.  3r31515. 3r31465. Changes in feature settings at project level 3r3-31502. 3r31468.  3r31515. 3r31465. 3r31365. Change group settings 3r350502. 3r31468.  3r31515. 3r31470. 3r31492.  3r31515. 3r31494.
Audit event documentation 3r3-31502. . 3r? 31503. 3r31492.  3r31515. 3r3r1378. Improvements in GitLab Helm chart
3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE) 3r3-31503. 3r31492.  3r31515. 3r31458.  3r31515. 3r31465. The LDAP and OmniAuth settings were unified in 3r31389. settings global 3r31391. 3r? 31502. that simplifies their change. Users who currently configure them separately for each nested charts will need to update their settings to upgrade to 11.5. 3r31468.  3r31515. 3r31465. Git v2 protocol is connected. 3r31468.  3r31515. 3r31465. 3r31399. Now supported
3r31401. GitLab Pseudonymizer
. 3r31468.  3r31515. 3r31465. Now available Maven package support. 3r31468.  3r31515. 3r31470. 3r31492.  3r31515. 3r31494. 3r31414. Documentation on the use of Helm charters 3r3-31502. 3r? 31503. 3r31492.  3r31515. 3r31419. Redesign of the activity bar
3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. In this release, we update the design of the activity panel to make it clearer who does what in your GitLab instance. New tape activity gives the reader more information about what happened, so you are always aware of events. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31432. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31437. The original ticket
. 3r? 31503. 3r31492.  3r31515. 3r31442. GitLab Runner ???r3r31443. 3r31492.  3r31515. 3r31494. (CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD)
3r31492.  3r31515. 3r31494. We also release GitLab Runner 11.5! GitLab Runner is an open source project that is used to run your CI /CD work and send the results back to GitLab. 3r? 31503. 3r31492.  3r31515. 3r31454. The most important changes: 3r31455. 3r31492.  3r31515. 3r31458.  3r31515. 3r31465. 3r31461. Support for raw (RAW) artifacts 3r3-331502. . 3r31468.  3r31515. 3r31465. 3r31466. The cause of the failure is now displayed when the execution timeout 3r3-31502. . 3r31468.  3r31515. 3r31470. 3r31492.  3r31515. 3r31494. A list of all changes can be found in CHANGELOG GitLab Runner. 3r? 31503. 3r31492.  3r31515. 3r31494. 3r31480. Documentation for GitLab Runner
. 3r? 31503. 3r31492.  3r31515. 3r31485. 3r31492.  3r31515. 3r31494. Detailed release notes and update /installation instructions can be found in the original English post: 3r31489. Access Control for Pages
released for GitLab 11.5. . 3r? 31503. 3r31492.  3r31515. 3r31494. worked on translation from English. cattidourden , 3r31497. Maryartkey
, 3r31499. ainoneko
and 3r31501. rishavant
. 3r? 31503. 3r31511. 3r31515. 3r31515. 3r31515. 3r? 31508. ! 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") () (); 3r3-31509. 3r31515. 3r31511. 3r31515. 3r31515. 3r31515. 3r31515.

+ 0 -

Add comment