GitLab 11.7 arrives with NPM registries and multi-level Child Epics
Another GitLab monthly release is here and it is stuffed with numerous new features and improvements. Most notably, release snapshots that not only include the source code but all related artifacts, are now available! Let’s have a look at the most interesting highlights.
A new GitLab release is here and, as usual, it brings tons of new features, major improvements, as well as announcing a number of deprecations that will be taking place in next couple releases and you should look out for.
But for now, let’s focus on all the new goodies shipped with GitLab 11.7.
Publish releases for your projects – Adds the ability to create releases in GitLab and view them on a summary page. Releases are a snapshot in time of the source, links, and other metadata or artifacts associated with a released version of your code, and allow for users of your project to easily discover the latest released version of your code.
Multi-level Child Epics – You can now have an epic containing both issues and epics. This allows you to create multi-level work breakdown structures.
Cross-project pipeline browsing – It is now possible to expand upstream or downstream cross-project pipelines right from the pipeline view, giving you visibility into your end-to-end pipelines, no matter in which project they start or finish.
Remediate vulnerability with patch file – You can now download a patch file, and apply it to your repo using the
git apply command. Then you can push changes back to your repository, and the security dashboard will confirm if the vulnerability is gone.
Configure Kubernetes app secrets as variables – Offers the ability to configure secrets as environment variables that are made available to the application running in your Kubernetes cluster. Simply prepend your variable with
K8S_SECRET_ and the relevant CI pipeline will take your application secret variable to populate a Kubernetes secret.
NPM registry – NPM registries built directly into GitLab. This being integrated right into GitLab would mean they can then share a simple package-naming convention to utilize that library in any Node.js project, and NPM and GitLab will do the rest, all from a single interface. Keep in mind, however, that this feature is available with GitLab Premium.
API support for Kubernetes integration – All the actions currently available in the GUI, such as listing, adding, and deleting a Kubernetes cluster are now accessible via the API. Teams can use this new functionality to fold in cluster creation as part of their workflow.
SEE ALSO: How well do you know your GitLab trivia?
In addition to these key features, GitLab 11.7 brings some more improvements to the table:
- Support catch-all email mailboxes including Microsoft Exchange and Google Groups for incoming email features
- Import issues CSV
- Short commit SHA available as environment variable
- Stricter self-approval restrictions
- Filter vulnerabilities in the Group Security Dashboard
- Show Dependency Scanning results in the Group Security Dashboard
- Include CI/CD files from other projects and templates
- RBAC mode default for Kubernetes cluster creation
- Support for private Go packages in subgroups
- Support for NGINX Ingress 0.16.0+ metrics
- GitLab Runner 11.7
There are, however, some deprecations you should look out for:
- Debian 7 Wheezy support – Removal date: Jan. 22, 2019
- Raspbian Jessie support – Removal date: Feb. 22, 2019
- CentOS 6 support for GitLab Runner – Removal date: Mar. 22, 2019
- Support for Prometheus 1.x in Omnibus GitLab – Removal date: Jun. 22, 2019
- OpenShift template for installing GitLab – Removal date: Jun. 22, 2019
- GitLab Geo will enforce Hashed Storage in GitLab 12.0 – Removal date: Jun. 22, 2019
Check out the official blog post for detailed information on all the new features, improvements, and deprecations.