GitLab has released version 13. 6 of the version management platform of the same name. For the code quality, the release shows a gradation of the relevance and effects of the respective problems. In addition, the branch and tag lists now show the status of the CI / CD pipeline (Continuous Integration, Continuous Delivery). Finally, the Visual Studio Code Extension brings additions for the integration with the source code editor.

In interaction with cloud services, automated distribution has recently been implemented possible on AWS Cloud Compute (EC2). Developers must activate Auto DevOps and the environment variables AWS_ACCESS_KEY_ID , AWS_SECRET_ACCESS_KEY for interaction with the AWS CloudFormation API. and AWS_DEFAULT_REGION define.

Is this critical or is it allowed to go through? For the detailed code quality report and for merge requests, the severity of the individual violations of the code quality can now be determined specify. In this way, critical issues that block the project from being rolled out can be distinguished more quickly from smaller problems.

Some Problems such as exceeding the maximum lines of code according to the project specifications are less critical than others.

(Image: GitLab)

The output of the report on the code quality in HTML format to make the information easier to share with others. The output files created in this format can be made available on GitLab Pages, among others.

Icons in the branch and tags list, which reflect the status of the CI / CD pipeline, are also intended to provide a better overview . So far, GitLab has only displayed the pipeline status via the separate view on the respective branch.

Connection to the editor For the interaction with Microsoft’s open source source code editor Visual Studio Code, the GitLab Extension offers some additions to the new release. Among other things, developers can now use GitLab snippets, i.e. saved blocks of code or text, directly in the editor. You can also view and comment on merge requests and issues directly from Visual Studio Code.

GtiLab Snippets can now be inserted directly into Visual Studio Code.

(Image: GitLab)

It is also worth mentioning that group administrators in GitLab now use the name of the first branch. The innovation is part of the concept of saying goodbye to “master” as a term with racist roots. In the version management Git since version 2. 13 the term is no longer hard-coded. GitLab has allowed individual customization for some time, but the control at group level is new.

Further additions in GitLab 13. 6 can be found in the GitLab blog. The new features listed are available in all editions of GitLab. In addition, as usual, some new functions only relate to the commercial versions. Among other things, the display of the code coverage for selected projects, which is included in the two most expensive categories Premium and Ultimate or Silver and Gold, is worth mentioning.

(rme)