Getting up and running with Gitlab's Continuous Integration can take less than 10 minutes (depending on what you want to do, YMMV) I'm going to show you how:

To begin with - I just want to setup a simple task that will runeslint on our code. Luckily for us, we're already half way there.

Starting from version 8.0, GitLab Continuous Integration (CI) is fully integrated into GitLab itself and is enabled by default on all projects.

If you head on over to a project within Gitlab and click onSettings andCD / CD (https://gitlab.com/{username}/{project}/settings/ci_cd) you will see a drop down forRunners. You should see two columns.Specific Runner andShared Runners. Awesome! (You don't have to do anything).

Runners

You should have some shared runners available. Shared runners are free to use for public open source projects and limited to 2000 CI minutes per month per group for private projects.

Runners are virtual machines that run jobs specified in a.gitlab-ci.yml. This file will tell the runner what jobs to do.

# At the root of your repository, add the .gitlab-ci.yml file.$touch .gitlab-ci.yml

Runners usedocker to pull animage and run our application in a container, so we need to tell it what image to pull, what things to install and what scripts to run.

Since I'm using node, we want to pull thatimage from Docker

# We're pulling and installing node into our virtual container, neat!image:node

Now we want to add astage. Stages tell the runner what functions to run and when. For example you might havebuild,test anddeploy stages. Stages can have multiple Jobs.

image:nodestage:# I just want to lint, so I will create a "lint" stage-lint# Lets name our Job eslint, because that's what it's doing.eslint:# tell eslint what stage it is. (This could also be build or test for example)stage:lint# What scripts do we want to run?script:# install eslint-npm i eslint# Run eslint-node_modules/eslint/bin/eslint.js .

Commit the.gitlab-ci.yml and push it to gitlab!

Head on over tohttps://gitlab.com/{username}/{project}/-/jobs to see your job in action.

Assuming you have some eslint errors, your job will fail - Woohoo!

But I have plugins, and presets!

You can simply install these along side thenpm i eslint statement.

If you have multiple, you can use a backslash\ to move it onto a new line for amultiline command

image:nodestages:-linteslint:stage:lintscript:# Install eslint-|npm install eslint \eslint-config-airbnb \eslint-config-prettier \eslint-plugin-flowtype \ # Any ideas on what I might want to do next?eslint-plugin-import \eslint-plugin-jsx-a11y \eslint-plugin-prettier \eslint-plugin-react# Run eslint-node_modules/eslint/bin/eslint.js .

Now go and get rid of all your eslint errors and you're on your way to a passing pipeline!