New stuff; fast stuff; safe stuff

GitLab 10.8 is here: Who said fast can’t be safe?

© Shutterstock / Prasetyo (modified)

GitLab is here once again to provide developers with efficient, fast and, most importantly, safer ways to deliver code!

With the release of 10.8, GitLab, once again, holds true to its principles of Getting Things Done. One new feature, one major improvement and a new addition to the GitLab’s open source codebase are the highlights of the new release.

Let’s have a closer look!


You know this stress that comes with releasing new features? The latest GitLab release aims to alleviate some of the anxiety with the new Incremental Rollouts feature that helps developers deploy code by exposing changes to only a subset of users. If you run into problems, you just roll back without affecting the entire user base! Easy peasy lemon squeezy!

That is some interactive security, right there!

GitLab’s built-in security automated functions include SAST, DAST, container scanning and dependency scanning. These features aim to help you stay one step ahead of any surfacing vulnerabilities. With GitLab 10.8, these security features become more interactive as you can now decide what action you want to take right through the security reports.

Open source, here we come!

Push Mirroring has been the most requested feature to move into GitLab’s open source code base and since GitLab takes these requests seriously, thy will be done! Push Mirroring is now open source; that opens up some pretty exciting opportunities, especially for freelance developers since they can now mirror each of their clients’ repos. What’s more, migrating to GitLab from other git-based repositories becomes significantly easier.

Check out what the Head of Product for GitLab had to say on what to expect of DevOps in 2018:

JAXenter: Do you think we’ll see more developers running containers in production on Kubernetes? 

Mark Pundsack: Containers are a core pillar of DevOps, but in 2018 they will hit a tipping point where we’ll see more developers running containers in production on Kubernetes than not.

JAXenter: Speaking of a DevOps context, what will the role of the cloud be? Are cloud computing architectural principles essential to DevOps success?

Mark Pundsack: I think that cloud computing poses a huge benefit to the success of DevOps. While it’s possible to do DevOps without cloud computing architectures, cloud-native is the basis for many successful DevOps transformations. Developers can schedule and orchestrate elastically and be more responsive and efficient by working with cloud architectures (whether in the public cloud or a cloud in your own datacenter).

For example, developing locally with Docker makes the transition to running in production much easier. And having an elastic cloud platform available during development allows developers to easily spin up ephemeral applications for testing as-needed rather than having to manage scarce shared resources.

JAXenter: Can containers enhance a company’s DevOps transformation? Is containerization part of the future of DevOps?

Mark Pundsack: It is hard to imagine a DevOps transformation that doesn’t involve containers. Containerization allows developers to move faster, optimize usage of resources and decouple code at the right granularity. Containers are a base-level part of DevOps and allow developers to ensure that their software will run, no matter where it is deployed. In 2017, it became clear that more developers and enterprises are using Kubernetes in production to assist with container management. In 2018, this trend will continue to prosper.

See the full interview here.

Eirini-Eleni Papadopoulou
Eirini-Eleni Papadopoulou was the editor for Coming from an academic background in East Asian Studies, she decided that it was time to go back to her high-school hobby that was computer science and she dived into the development world. Other hobbies include esports and League of Legends, although she never managed to escape elo hell (yet), and she is a guest writer/analyst for competitive LoL at TGH.

Inline Feedbacks
View all comments