Customer Testimonials

Updated 2019-11-06

Delta Airlines uses GitLab on its journey to cloud native and workflow portability, and uses Red Hat OpenShift as their deployment platform.

Athlinks uses GitLab end-to-end, including Epics and Issues all the way through CI/CD. Presentation from GitLab Connect Denver in 2019.

Overriding Auto Devops

GitLab Auto Devops provides a powerful set of features out-of-the-box that works with no CI configuration at all. It’s useful for demos, or for learning about best practices for GitLab CI. But most customers need to modify the devops pipeline to suit there needs. Fortunately, we don’t have to start from scratch. We can include Auto Devops and override it. How to override To override Auto Devops, make sure that: [Read More]

Require a CI Job to Run Before Merge, But Not on Every Commit in the MR

Jobs in GitLab CI/CD can be set to run “manually” using the following option: when: manual, which looks something like this in the Pipeline view: … requiring interaction from a user to proceed. Note that all of the examples below are tested in the context of a Merge Request using the only: merge_requests setting on all the jobs. Pipeline Status The status of the pipeline itself while waiting for manual intervention depends on a few things. [Read More]

GitLab Auto Devops

Auto Devops is a GitLab feature set that encapsulates best practices for GitLab CI/CD and exercises many of GitLab’s most powerful features. The Auto Devops package in its entirety consists of: CI configuration templates for common jobs such as build, test, and deploy CI configuration templates for security jobs such as SAST and container scanning A master CI configuration template that includes and runs all the above Some Docker images that are used during the build and deploy processes A Helm chart used for deployment to Kubernetes All of the above code is released under an open source license. [Read More]

Docker Container Registry and GitLab CI

The Container Registry is a powerful feature of GitLab that acts as a private Docker Registry for passing images between jobs within a pipeline, between pipelines, or for use outside of GitLab CI/CD. Note that GitLab CI/CD doesn’t automatically use the Container Registry; it has to be accessed explicitly from within jobs. Auto Devops uses it somewhat, but not entirely as designed; the Docker CI/CD template pushes to it but doesn’t pull from it. [Read More]

Jenkins - Integrate or Replace?

First, if your organization currently uses Jenkins and has Jenkins pipelines defined, we recommend integrating GitLab with Jenkins so teams can continue running their jobs after switching SCM platforms. Refer to the Jenkins CI Service Documentation for information on how to use the GitLab Plugin for Jenkins. Once GitLab is up and running, new projects and teams can use GitLab CI/CD immediately. Most developers find it much easier to get started with GitLab CI/CD than with Jenkins. [Read More]