GitLab 11.0 is here with the treasure of Auto DevOps
It is time for all of us to live the DevOps dream! GitLab 11.0 is here and it brings with it the essence of what DevOps strives to achieve the most: automation!
What is the essence of DevOps? That’s right, you guessed it: automation! This time, GitLab has taken an even bigger step towards Getting Things Done!
The newest GitLab version 11.0 is here with Auto DevOps. What is Auto DevOps you ask? It is a pre-built, fully featured CI/CD pipeline that automates the entire delivery process and it is generally available in GitLab 11.0.
Auto DevOps covers the end-to-end lifecycle, meaning that all you have to do is commit your code to GitLab and Auto DevOps will do the rest for you. More precisely, the building, testing, code quality scanning, security scanning, license scanning, packaging, performance testing, deploying, and monitoring processes are now automated!
But that’s not all! GitLab 11.0 comes with some more handy features:
License management: automatically detects licenses of a project’s dependencies
Testing: enhanced security testing of code, containers, and dependencies
Kubernetes: further integration features
Web IDE: ability to view your CI/CD pipelines from the IDE and get immediate feedback if a pipeline fails
Epic and Roadmap: updated Epic/Roadmap navigation interface that makes it easier to see the big picture and make planning easier
SEE ALSO: Have you met the GitLab Web IDE yet?
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.