GitLab 11.8 arrives with error tracking and SAST for JavaScript

Share
  • February 25, 2019

Another month is about to end and so it is time for a new GitLab release!

GitLab 11.8 features a truly extensive list of new features, changes, and improvements. As per usual, in this article, we will have a look at the most interesting highlights featured in the latest release as well as some upcoming deprecations you should keep an eye on.

Let’s get started!

The highlights

JavaScript coverage in SAST – Building on top of our existing node.js support. Now any JavaScript file can be scanned, like static scripts and HTML. A vital practice in DevSecOps is to scan code changes with each commit, and this change covers one of the most popular web languages, helping you to find JavaScript risks as early as possible.

Error tracking with Sentry – More convenient and efficient to monitor errors by integrating with popular open source error tracker Sentry, and displaying the most recent errors right within your GitLab project.

Merge Request Approval Rules – Allow you to better communicate who should participate in code reviews by specifying the eligible approvers and the minimum number of approvals for each. Approval rules are shown in the merge request widget so the next reviewer can quickly be assigned.

Improved cross-project pipeline triggers – Added first-class support for triggering these downstream pipelines with the trigger: keyword, which can be added to a bridge job to automatically trigger a downstream pipeline when the current pipeline succeeds.

Auto DevOps support for environment-specific custom domain – You can now use the environment variable ADDITIONAL_HOSTS to specify one or more custom domains for your application. Furthermore, you can scope it to a specific environment by prepending the environment name to the variable, ie. _ADDITIONAL_HOSTS.

Show function scale for Knative functions – You can now see the scale of your serverless deployments for each application or function deployed to your Knative instance. Scale is illustrated by the number of Kubernetes pods currently in use.

But that is not all!

In addition to these main features, GitLab 11.8 also brings some improvements to the table:

  • Upgrade Kubernetes Runner application via Kubernetes integration
  • Redesigned related merge requests, consistent with related issues
  • Child Epics in Epics API
  • Move Auto DevOps domain from CI/CD settings to cluster settings
  • .html extensions are now automatically resolved for Pages sites
  • Predefined Pages variables in CI
  • Gitaly support for TLS
  • Add tolerations to Kubernetes executor
  • Gitaly support for Elasticsearch
  • Force re-deploy when Auto DevOps application secrets are updated
  • Ensure Cert-Manager works with Auto DevOps URLs

SEE ALSO: GitLab Serverless: A new single-application DevOps experience

Last but not least, make sure to check out the upcoming deprecations announced with GitLab 11.8.

  • GitLab 11.8 is the last release with support for Raspbian Jessie – Removal date: Feb. 22, 2019
  • Runner support for CentOS 6 when using the Docker executor will be removed in GitLab 11.9 – Removal date: Mar. 22, 2019
  • With GitLab 12.0, any installation not yet running Prometheus 2.0 will be automatically upgraded – Removal date: Jun. 22, 2019
  • TLS v1.1 will be disabled by default in 12.0 – Removal date: Jun. 22, 2019
  • GitLab Geo will enforce Hashed Storage in GitLab 12.0 – Removal date: Jun. 22, 2019

Head over to the official release notes to find out more information about all the new features, changes and deprecations.

The post GitLab 11.8 arrives with error tracking and SAST for JavaScript appeared first on JAXenter.

Source : JAXenter