GitLab 11.10 releases with enhanced operations dashboard, pipelines for merged results and much more!

2 min read

Yesterday, the team at GitLab released GitLab 11.10, a web-based DevOps lifecycle tool. This release comes with new features including pipelines on the operations dashboard, pipelines for merged results, and much more.

What’s new in GitLab 11.10?

Enhanced operations dashboard

GitLab 11.10 enhances the operations dashboard with powerful feature that provides an overview of pipeline status. This becomes useful while looking at a single project’s pipeline as well as for multi-project pipelines. With this release, users can now get instant visibility at a glance into the health of all of the pipelines on the operations dashboard.

Run pipelines against merged results

Users can now run pipelines against the merged result prior to merging. This allows the users to quickly catch errors for much quicker resolution of pipeline failures and more efficient usage of GitLab Runners. By having the merge request pipeline automatically create a new ref that contains the combined merge result of the source and target branch, it is possible to have the combined result valid.

Scoped labels

Scoped labels allow teams to use apply labels on issues, merge requests, and epics and custom workflow states. These labels can be configured by using a special double colon syntax in the label title.

Few users think that new updates won’t be as successful as the team expects it to be and there is still a long way to go for GitLab. A user commented on HackerNews, “Can’t help but feel that their focus on moving all operation insights into gitlab itself will not be as successful as they want it to be (as far as I read, their goal was to replace their operations and monitoring tools with gitlab itself[1]). I’ve worked with the ultimate edition for a year and the kubernetes integration is nowhere close to the insight you would get from google, amazon or azure in terms of insight and integration with ops-land. I wish all these hours were spent on improving the developer lifecycle instead.”

Few others are happy with this news and they think that GitLab has progressed well. A comment reads, “GitLab has really come a long way in the past few years. The days of being a github-alike are long gone. Very happy to see them continue to find success.”

To know more about this news, check out GitLab’s post.