Geekly Articles each Day
📜 ⬆️ ⬇️

GitLab 11.10


GitLab 11.10 with control panel pipelines, pipelines for combined results and multiple-line sentences in Merge Requests.


Convenient information about the performance of pipelines in different projects


GitLab continues to increase the transparency of the DevOps life cycle. In this release , an overview of the status of the pipelines has been added to the control panel .


This is convenient, even if you are studying a single project pipeline, but it is especially useful if there are several projects - and this usually happens if you use microservices and want to launch the pipeline for testing and delivering code from different project repositories. Now you immediately see the performance of the pipelines on the control panel , wherever they are executed.


Run pipelines for combined results


Over time, the source and target branches diverge, and there may be a situation when, separately, they cope and do not work together. Now you can run pipelines for the combined results to merge . So you will quickly notice errors that would manifest themselves only if changes are often moved between branches, which means that you will be much faster to fix pipeline errors and use GitLab Runner more effectively.


Further collaboration optimization


GitLab 11.10 has even more options for easy collaboration and simplified workflows. In the previous issue, we introduced proposals for Merge Requests, when the reviewer could propose a change to one line in the comment to the Merge Request, and it could be immediately committed directly from the comment thread. Our users liked it, and they asked to expand this feature. Now you can suggest changes for several lines , indicating which lines to delete and which ones to add.


Thanks for your feedback and suggestions!


And that is not all...


There are so many amazing features in this release, for example, shortcuts in a certain area , more thorough cleaning of the container registry , composable Auto DevOps and the ability to buy extra minutes for CI Runner . Below are the details about each of them.


This month’s most valuable employee ( MVP ) - Takuya Noguchi

This month, Takuya Noguchi has become the most valuable employee. Takuya did a good job to the glory of GitLab : fixed bugs, completed flaws in the backend and frontend, and improved the user interface. Thank!

The main features of GitLab 11.10


Control Panel Pipelines


PREMIUM, ULTIMATE, SILVER, GOLD


The control panel in GitLab displays project information for the entire GitLab instance. You add individual projects one by one and you can choose which project interests you.
In this release, we added information about the status of the pipelines to the control panel. Now developers see the efficiency of the pipelines in all the necessary projects - in one interface.



Pipelines for combined results


PREMIUM, ULTIMATE, SILVER, GOLD


Over time, the source branch usually deviates from the target, unless you constantly move changes between them. As a result, the source and target pipelines of the “green” branches and merge conflicts do not arise, but the merge fails due to incompatibility of changes.


When the Merge Requests Pipeline automatically creates a new link that contains the merged result of the source and target branches, we can launch the Pipeline via this link and ensure that the overall result will be working.


If you are using Merge Requests pipelines (in any capacity) and use private GitLab runners of version 11.8 or later, you need to update them so that gitlab-ee # 11122 does not have a problem. This does not affect the users of the public GitLab runners.



Proposing changes in multiple lines


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


When you work together on Merge Requests, you often notice problems and offer solutions. Since GitLab 11.6, we have supported the suggestion of changes for a single line.


In version 11.10, you can suggest changes for several lines in the comments to the diff Merge Request, and then any user with write permissions to the source branch can accept them with one click. Thanks to the new feature, you can avoid copy-paste, as in previous versions.



Labels in one area


PREMIUM, ULTIMATE, SILVER, GOLD


With labels in one area, teams can apply mutually exclusive labels (in the same area) for a task, merge-requester or epic in scenarios with custom fields or custom workflow states. They are configured using a special syntax with a colon in the label header.


Suppose you need a custom field in tasks to track the operating system of the platform that your functions are aimed at. Each task should relate to only one platform. You can create the shortcuts platform::iOS , platform::Android , platform::Linux and others as needed. If you apply one such shortcut to the task, another existing shortcut that starts with platform:: . Is automatically deleted.


Suppose you have workflow::development , workflow::review and workflow::deployed shortcuts to indicate the status of the workflow in your team. If the task already has a workflow::development shortcut, and the developer wants to transfer the task to the workflow::review stage, he simply applies the new shortcut, and the old one ( workflow::development ) is automatically deleted. This behavior already exists when you move tasks between lists of shortcuts on the task board, which represents the workflow of your team. Now team members who do not work directly with the task board can change the state of the workflow in the tasks themselves.



More thorough cleaning of the registry of containers


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


In normal use of the registry of containers with CI pipelines, you send several separate changes to a single tag. Due to the implementation of the Docker distribution, the default behavior is to save all changes in the system, but in the end they take up a lot of memory. If you use the -m option with registry-garbage-collect , you can quickly remove all previous changes and free up valuable space.



Buying extra minutes for CI Runner


BRONZE, SILVER, GOLD


Users with GitLab.com paid plans (Gold, Silver, Bronze) can now buy additional CI Runner minutes. Previously, it was necessary to keep within the quota stipulated by the plan. Thanks to this improvement, you can pre-purchase minutes above the quota to avoid interruptions in work due to the shutdown of the pipelines.


Now 1000 minutes cost 8 dollars, and you can buy them all you want. Additional minutes will begin to be spent when you spend the entire monthly quota, and the balance of the additional minutes is transferred to the next month. In a future release, we want to add this feature to free plans.



Composable Auto DevOps


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


With Auto DevOps, teams move to modern DevOps practices almost effortlessly. Starting with GitLab 11.10, every job in Auto DevOps is provided as an independent template . Users can use includes in GitLab CI to enable separate Auto DevOps stages and still use their custom gitlab-ci.yml . Thus, you can include only the necessary jobs and enjoy the benefits of upgrades in upstream.



Automatic Group Management on GitLab.com with SCIM


SILVER, GOLD


Previously, you had to manually manage groups on GitLab.com. You can now use SAML SSO and manage groups using SCIM to create, delete and update users on GitLab.com.


This is especially useful for companies with a large number of users and centralized identity providers. Now you can have a single source of truth, for example, Azure Active Directory, and users will be created and deleted automatically through an identity provider, rather than manually.



Log in to GitLab.com through a SAML provider


SILVER, GOLD


Previously, when using SAML SSO for groups, the user had to log in with GitLab credentials and identity provider. You can now directly log in via SSO as a GitLab user associated with a configured group.


Users will not have to log in twice, so companies are more comfortable using SAML SSO for GitLab.com.



Other improvements in GitLab 11.10


Scheme of child epics


ULTIMATE, GOLD


In the previous issue, we added child epics (epic epic) to make it easier for you to manage the structure of the distribution of tasks. Child epics are displayed on the parent epic page.


In this release, a diagram of child epics is displayed on the parental epic page, so commands see the chronology of child epics and can manage time dependencies.



Merge Requests pop-up screens


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


In this issue, we present informative screens that pop up when you hover over a Merge-Retrieval link. Previously, we showed only the header of the merge-requester, and now also the status of the merge-requester, the status of the CI pipeline and the short URL.


In future releases, we plan to add more important information, for example, responsible persons and control points , and also introduce pop-up screens for tasks .



Filtering Merge Requests by Target Branches


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


Git workflows for software release or delivery are often associated with several long-term branches — to make corrections to previous versions (for example, stable-11-9 ) or to move from quality to production (for example, integration ), but it’s not so easy to find merge requisitions for these branches among the many open merge requisitions.


The list of merge requisitions for projects and groups can now be filtered by the target branch of the merge requisition, to make it easier to find the right one.


Thank you, Hiroyuki Sato!



Sending and merge with a successful pipeline


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


If we use Trunk-based development, we should avoid long-lived branches in favor of small one-owner temporary branches. Minor changes are often sent directly to the target branch, but at the same time we risk breaking the build.


In this release, GitLab supports new send options in Git to automatically open merge requesting, set the target branch and ensure merge when the pipeline is successful from the command line when sending to the branch.



Improved integration with external dashboards


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


GitLab can access multiple Prometheus servers (at the environment, project, and group (expected) ), but having multiple endpoints can complicate the system or not be supported by standard dashboards. In this release, teams can use the same Prometheus API, which greatly simplifies integration with services such as Grafana.


Sort Wiki pages by creation date


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


In the project's Wiki, teams can share documentation and other important information along with source code and tasks. In this release, the list of pages on the Wiki can be sorted by creation date and title to quickly find newly created content.



Monitoring resources requested by the cluster


ULTIMATE, GOLD


GitLab helps monitor the Kubernetes cluster for development and production applications. Starting with this release, keep track of the processor resources and memory requested by the cluster to notice potential difficulties until they become problems.



View load balancer metrics in Grafana dashboards


CORE, STARTER, PREMIUM, ULTIMATE


It is very important to monitor the health of the GitLab instance. Previously, we provided default dashboards through the built-in instance of Grafana. Starting with this release, we have included additional panels for monitoring NGINX load balancers.


SAST for Elixir


ULTIMATE, GOLD


We continue to expand language support and deepen security checks. In this release, we have included security checks for projects on Elixir and projects created on the Phoenix platform .


Multiple queries in one chart


PREMIUM, ULTIMATE, SILVER, GOLD


In GitLab, you can create charts to visualize metrics that are collected. Often, for example, if you want to see the maximum or average value of a metric, you want to display several values ​​in one diagram. From this release you have this opportunity.


DAST results on group security panel


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


We have added Dynamic Application Security Testing (DAST) results to the group security panel in addition to SAST, container scanning and dependency scanning.


Add Metadata to Container Scan Report


ULTIMATE, GOLD


In this release, the container scan report contains more metadata — we added the affected component (the Clair feature) to the existing metadata: priority, identifier (with reference to mitre.org) and the affected level (for example, debian: 8).


Adding a metrics report type to Merge Requests


PREMIUM, ULTIMATE, SILVER, GOLD


GitLab already provides several types of reports that can be included directly in merge requests: from code quality reports and unit testing during the verification phase to SAST and DAST during the protection phase.


Although these are important reports, basic information suitable for different scenarios is also needed. In GitLab 11.10, we provide metrics reports right in the merge requester, which expects a simple key-value pair. In this way, users track changes over time, including user metrics, and changes in metrics for a specific merge-quest. Memory usage, testing of specialized loads and health statuses can be transformed into simple metrics that can be viewed directly in Merge Requests along with other embedded reports.


Maven multimodule support for dependency scanning


ULTIMATE, GOLD


In this release, Maven multimodule projects support GitLab dependency scanning. Previously, if a submodule had a dependency on another submodule of the same level, it could not allow the download from the central Maven repository. Now the Maven multi-module project is created with two modules and a dependency between two modules. Dependencies between modules of the same level are now available in the local Maven repository so that the build can continue.


Users can change the path for cloning in CI


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


By default, GitLab Runner clones a project into a unique nested path in $CI_BUILDS_DIR . But for some projects, such as Golang, the code needs to be cloned into a specific directory so that it can be collected.


In GitLab 11.10, we introduced the variable GIT_CLONE_PATH , with which you can specify a specific path where GitLab Runner clones the project before performing the task.


Simple masking of protected variables in logs


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


GitLab provides several ways to protect and limit the scope of variables in GitLab CI / CD. But variables can still intentionally or accidentally get into the build logs.


GitLab is serious about risk management and auditing and continues to add features to comply. In GitLab 11.10, we introduced the ability to mask certain types of variables in the job trace logs by adding a level of protection against accidental content of these variables in the logs. And GitLab now automatically masks many of the built-in token variables.


Enabling and disabling Auto DevOps at the group level


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


With Auto DevOps in the GitLab.com project, you can take on modern DevOps workflows — from assembly to delivery — without unnecessary trouble.


Starting from GitLab 11.10, you can enable or disable Auto DevOps for all projects in the same group.


Simplified and improved license page


STARTER, PREMIUM, ULTIMATE


To manage the license keys was more convenient and easier, we changed the design of the license page in the admin panel and highlighted the most important elements.



Updated Deployable Tags in the Kubernetes Cluster


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


Deployable boards give an idea of ​​deployments in the Kubernetes cluster.


In this issue, we have changed the way in which labels relate to deployments. Deployable boards are now looking for the app.example.com/app and app.example.com/env or app app.example.com/env . This will avoid filtering conflicts and reduce the risk of incorrect samples for displaying on the boards.


In addition, in GitLab version 12.0, we plan to abandon support for the app label from the Kubernetes Deploye selector , and a match will be possible only by app.example.com/app and app.example.com/env .


Dynamic Kubernetes resource creation


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


The integration of Kubernetes into GitLab allows you to use the RBAC function using the service account and allocated namespace for each GitLab project. Starting with this release, for maximum efficiency, these resources will be created only when needed for deployment.


With Kubernetes Deploy, GitLab CI will create these resources before deploying.


Group runners for clusters at the group level


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


Group-level clusters now support the installation of GitLab Runner. At the group level, Kubernetes runners are displayed for child projects as group runners labeled cluster and kubernetes .


Call Counter for Knative Functions


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


The functions deployed with GitLab Serverless now show the number of calls received for a particular function. To do this, install Prometheus on the cluster where Knative is installed.



Monitoring git clean for Jobs GitLab CI / CD


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


By default, GitLab Runner performs git clean in the process of unloading code when running the job in GitLab CI / CD. Starting from GitLab 11.10, users can control the parameters passed to the git clean command. This is convenient for teams with dedicated runners, as well as for teams that collect projects from large mono-repositories. Now they can manage the upload process before executing the scripts. The new variable GIT_CLEAN_FLAGS defaults to -ffdx and accepts all possible parameters of the [git clean](https://git-scm.com/docs/git-clean) command [git clean](https://git-scm.com/docs/git-clean) .


Core External Authorization


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


Protected environments may require an additional external authorization resource to access the project. We added support for an additional level of access control in 10.6 and received many requests to open this functionality in Core. We are pleased to provide external authorization and an additional level of security for Core instances, since this feature is needed by individual participants.


Ability to create projects in groups in Core


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


The Developer role can create projects in groups since version 10.5 , and now it is possible in Core. Creating projects is a key opportunity for productive work in GitLab, and thanks to the inclusion of this feature in Core, it is now easier for the instance team to do something new.


GitLab Runner 11.10


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


Today we released GitLab Runner 11.10! GitLab Runner is an open source project that is used to run CI / CD jobs and send the results back to GitLab.


The most interesting changes:



A complete list of changes can be found in the GitLab Runner change log: CHANGELOG .


Fix project_id returned in blob search API in Elasticsearch


STARTER, PREMIUM, ULTIMATE


We fixed a bug in the blob search API in Elasticsearch, which mistakenly returned 0 for project_id . You will need to reindex Elasticsearch to get the correct project_id values ​​after installing this version of GitLab.


Omnibus Improvements


CORE, STARTER, PREMIUM, ULTIMATE


We made the following improvements to Omnibus in GitLab 11.10:



Performance improvements


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


We continue to improve GitLab performance with each release for GitLab instances of any size. Some improvements in GitLab 11.10:



GitLab Chart Improvements


CORE, STARTER, PREMIUM, ULTIMATE


We made the following improvements to the GitLab diagrams:



Obsolete features


GitLab Geo will provide hash storage in GitLab 12.0


GitLab Geo requires hashed storage to mitigate competition on secondary nodes. This was noted in gitlab-ce # 40970 .


In GitLab 11.5, we added this requirement to the Geo documentation: gitlab-ee # 8053 .


In GitLab 11.6, sudo gitlab-rake gitlab:geo:check checks whether hashed storage is enabled and all projects are migrated. See gitlab-ee # 8289 . If you are using Geo, please run this check and migrate as soon as possible.


In GitLab 11.8, the constantly disabled warning gitlab-ee! 8433 will be displayed on the Admin Area › Geo › Nodes page if the above checks are not allowed.


In GitLab 12.0, Geo will use hashed storage requirements. See gitlab-ee # 8690 .

Date of deletion: June 22, 2019


Ubuntu 14.04 support


GitLab 11.10 will be the latest release with Ubuntu 14.04 support .


Canonical has announced the discontinuation of standard Ubuntu support on 14.04 from April 2019 . We advise users to upgrade to a supported version of LTS: Ubuntu 16.04 or Ubuntu 18.04.


Date of deletion: May 22, 2019


Limiting the maximum number of pipelines created by a single shipment


GitLab HEAD . , (, develop ).


, (, , ), . GitLab 11.10 4 .


: 22 2019 .


legacy GitLab Runner


Gitlab 11.9 GitLab Runner / . GitLab Runner , . .


GitLab 11.0 GitLab Runner. metrics_server listen_address GitLab 12.0. .


11.3 GitLab Runner - ; S3 . , . .


GitLab 12.0. , , , GitLab 11.9+ GitLab Runner 12.0.


: 22 2019 .


GitLab Runner


11.4 GitLab Runner FF_K8S_USE_ENTRYPOINT_OVER_COMMAND , #2338 #3536 .


GitLab 12.0 , . .


: 22 2019 .


Linux, EOL, GitLab Runner


Linux, GitLab Runner, .


GitLab 12.0 GitLab Runner Linux. , , . ( Javier JardĂłn ) !


: 22 2019 .


GitLab Runner Helper


Windows Docker executor , helper image .


GitLab 12.0 GitLab Runner . , helper image . .


: 22 2019 .


legacy git clean GitLab Runner


GitLab Runner 11.10 , Runner git clean . , git reset git clean .


, FF_USE_LEGACY_GIT_CLEAN_STRATEGY . true , legacy- . GitLab Runner .


GitLab Runner 12.0 legacy- . .


: 22 2019 .


System Info


GitLab GitLab admin/system_info , .


GitLab 12.0 .


: 22 2019 .



:



Installation


GitLab, GitLab .


Update


.


GitLab


GitLab : SaaS .


: .



SaaS — GitLab.com : , GitLab .



')

Source: https://habr.com/ru/post/450378/

More articles:


All Articles