GitLab 11.10 arrives with enhanced streamline collaboration, pipelines for merged results & more
Another month is nearly gone and that means that it is time to have a look at a new GitLab release. GitLab 11.10 arrives with a long list of new features and improvements including pipelines on the Operations Dashboard and pipelines for merged results. Let’s have a look.
Punctual as always, at the end of each month GitLab comes back with a new release. Today, we take a look at the latest update with GitLab 11.10.
Among others, this month’s release brings new features that help developers monitor pipeline health across projects, run pipelines against merged results and more.
Let’s have a look at some of the highlights.
What’s new in GitLab 11.10
Pipelines on the Operations Dashboard – You can now view the pipeline health of the projects you want in a single interface.
Pipelines for merged results – Now, merge request pipeline automatically creates a new ref that contains the combined merge result of the source and target branch. It then runs the pipeline against this reference, ensuring that the combined result is valid.
Suggest changes to multiple lines – With this release, changes can be suggested to multiple lines when leaving a comment on a merge request diff.
More thorough Container Registry cleanup – Administrators now have an easier way to wipe out historical revisions and free up valuable storage space by using the
-m parameter with
Composable Auto DevOps – Each job of Auto DevOps is now available as an independent template. This means that using the
includes feature of GitLab CI, users can include only certain stages of Auto DevOps while continuing to use their own custom
In addition to these new features, there are some other noteworthy improvements going live with GitLab 11.10, including:
- Child Epics roadmap
- Push and merge when pipeline succeeds
- SAST for Elixir
- Multi-module Maven projects support for Dependency Scanning
- Enable/disable Auto DevOps at the Group level
- Just-in-time Kubernetes resource creation
- Add control for
git cleanflags for GitLab CI/CD jobs
- Fix returned
project_idin blob search API with Elasticsearch
- GitLab Runner 11.10
Last but not least, we should have a look at some deprecations that are about to take place:
- GitLab Geo will enforce Hashed Storage in GitLab 12.0 – Removal date: June 22, 2019
- GitLab 11.10 is the last release with support for Ubuntu 14.04 – Removal date: May 22, 2019
- Starting with GitLab 11.10, there will be a maximum of 4 pipelines during a push operation – Removal date: May 22, 2019
metrics_serverwill be removed in favor of
listen_addressin GitLab 12.0 – Removal date: June 22, 2019
- Starting with GitLab Runner 12.0, there will be no support for the legacy cleanup strategy and remove the ability to restore it with a feature flag – Removal date: Jun. 22, 2019
If you want to have a look at the full list of new features, improvements, and deprecations, head over to the official blog post.