Include external files in CI/CD pipeline definition
GitLab CI/CD pipelines are defined in a YML definition file that is stored in the project’s repository. Many times you are using the same job definitions for many different projects, or just copying and pasting existing snippets from examples and documentation.
With GitLab 10.5 you can now import other files into your main configuration using
include keyword. These files can be both local files on the same repository,
or remote files that are publicly accessible via HTTP/HTTPS. Security checks and
deployment configurations are common examples of jobs that can be reused and shared.
Gemnasium dependency checks
GitLab recently acquired Gemnasium and since then we have worked together to integrate this awesome technology into our security testing features.
Thanks to the advanced detection and the database of existing vulnerabilities, with GitLab 10.5 you can now receive very accurate security reports for dependencies of your application for the following languages:
- Java (Maven)
If you are already using Auto DevOps, you don’t need to change anything. If you copied the job definition to your pipeline, you can update it to support the latest features. See the example page for more information.
Track additional browser performance metrics
In GitLab 10.3, we added the ability to quickly determine the performance impact of merge request with Browser Performance Testing. With this release we are analyzing three additional metrics for changes: speed index, transfer size, and number of requests.
We have also added the capability to persist the full sitespeed.io report as an artifact, allowing developers and reviewers easy access to a trove of performance and debugging information. If you are using Auto DevOps, the report will be automatically saved for you.
Git LFS 2 locking support
Git LFS 2.0.0 added file locking support to Git LFS. It is now supported by GitLab, allowing LFS files to be locked using the Git LFS client. Locked files are easily identified by the lock icon.
Support for locking any file or directory was added to GitLab Premium 8.9, allowing files to be locked through the GitLab interface. Git LFS locking has been integrated with GitLab file locking in GitLab Premium 10.5.