GitLab 12.4 pushes merge request dependencies, governance

GitLab 12.4 pushes merge request dependencies, governance
Gitlab Logo

GitLab has rolled out its latest iteration, with the emphasis this time round on merge request dependencies and a whole pile of governance features.

The DevSecEverythingOps vendor chose to highlight the introduction of merge request dependencies in the 12.4 release. As it says on the tin, this will allow dependencies to be defined in merge requests, which should prevent changes “being merged in the wrong order while also improving the visibility of dependencies during code review.”

The feature was originally debuted as Cross-Project Merge Request Dependencies in 12.2, but has been expanded to support more types of dependencies, and dependencies within the same project.

The release also includes a slew of features aimed at governance.

An API for instance level audit events has been included – GitLab says these are “a powerful way to better understand adherence to policies”, and the API will mean admins “can obtain events programmatically and better enable powerful alerting and monitoring that meets specific needs.”

Admins also now get Pages access control on GitLab.com, something that was previously only available on the self-hosted platform.

The third governance feature is code owner approval for protected branches, which makes it possible to “prevent directly pushing changes to files or merging changes without the code owner’s approval for specific branches.”

There are a raft of other changes. 

Kubernetes fans – which is everyone these days, isn’t it? – now have the ability to enable Cloud Run on GKE with a single click, automatically provisioning the cluster with Knative, Istio and http load balancing. GitLab adds the feature will be rebranded as Cloud Run for Anthos as of next month. The new release also adds the option of one-click install for Group Runner on Kubernetes.

Pod logs can now be viewed from any environment, and GitLab has promised the ability to create a logging link directly from the Operations menu in a future release.

You can see the full list of changes – including a few deprecations – at GitLab here.