Ask Sendai

Automation is essential for successful DevOps teams, and CI/CD pipelines are a big part of that journey. At its most basic level, a pipeline gets code from point A to point B. What makes a better pipeline is how quickly and efficiently it accomplishes this task. A CI/CD pipeline automates steps in the SDLC like builds, tests, and deployments. When a team takes advantage of automated pipelines, they simplify the handoff process and decrease the chance of human error, creating faster iterations and better quality code. Everyone can see where code is in the process and identify problems long before they make it to production. In GitLab 9.3 we made it possible to display links for upstream and downstream projects directly on the pipeline graph, so developers can check the overall status of the entire chain in a single view.

GitLab 12.0 marks a key step in our journey to create an inclusive approach to DevSecOps, empowering ‘everyone to contribute’. For the past year, we’ve been on an amazing journey, collaborating and creating a solution that brings teams together. There have been thousands of community contributions making GitLab more lovable. We believe everyone can contribute, and weâve enabled cross-team collaboration, faster delivery of great code, and bringing together Dev, Ops, and Security. GitLab review applications are a fantastic tool to enable stakeholders from Operations to QA to business owners to evaluate and approve application changes before production. In GitLab 12.0, we make it easy to provide visual feedback directly from the review app.

Serverless is the latest innovation in cloud computing that promises to alter the cost-benefit equation for enterprises. As our CEO, Sid Sijbrandij says, ‘All roads lead to compute.’ There is a race among providers to acquire as many workloads from enterprises as possible, at the cheapest cost. The latter is where serverless comes in: serverless computing is an execution model in which the cloud provider acts as the server, dynamically managing the allocation of machine resources. Pricing is based on the actual resources consumed by an application, rather than on pre-purchased units of capacity. This field began with the release of AWS Lambda in November 2014.