From 2d16638220c59eb80b2fd11a9bf73dba48d01913 Mon Sep 17 00:00:00 2001 From: Tomas Norre Mikkelsen Date: Thu, 8 Mar 2018 19:50:58 +0100 Subject: [PATCH] [TASK] Added Gitlab CI to Tools (assess) --- radar/2017-10-01/gitlab-ci.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 radar/2017-10-01/gitlab-ci.md diff --git a/radar/2017-10-01/gitlab-ci.md b/radar/2017-10-01/gitlab-ci.md new file mode 100644 index 0000000..c519824 --- /dev/null +++ b/radar/2017-10-01/gitlab-ci.md @@ -0,0 +1,16 @@ +--- +title: "Gitlab CI" +ring: assess +quadrant: tools +--- + +Till now we have been using [Jenkins](https://jenkins.io/) for almost every single task that we have automated. With [Gitlab CI](https://about.gitlab.com/features/gitlab-ci-cd/) on the market, we get quite a number of new possibilities. + +Some of the highlights are: + +* Multi-platform: you can execute builds on Unix, Windows, OSX, and any other platform that supports Go. +* Multi-language: build scripts are command line driven and work with Java, PHP, Ruby, C, and any other language. +* Pipeline: you can define multiple jobs per stage and you can trigger other builds. +* Autoscaling: you can automatically spin up and down VM's to make sure your builds get processed immediately and minimize costs. +* Build artifacts: you can upload binaries and other build artifacts to GitLab and browse and download them. +* Docker support: you can use custom Docker images, spin up services as part of testing, build new Docker images, even run on Kubernetes.