website/content/blog/gitlabcicd.md

---
title: "Gitlab CI/CD"
date: 2019-07-01T21:36:56-04:00
draft: false
medium_enabled: true
---

One of the greatest benefits I believe of integrating Gitlab's CI/CD into your workload is code linting and building. This immediately eliminates the easy mistakes that developers make and wastes less people's time.

I'm working towards getting the build setup just right in one of the projects I'm currently working. However, in the meantime, Gitlab supports running it's CI/CD jobs under the `shell executor`. I would like to go to the default Docker route in the future once I figure out all of the dependencies of the project I'm building.
Website snapshot 2020-01-15 21:51:49 -05:00			`---`
			`title: "Gitlab CI/CD"`
			`date: 2019-07-01T21:36:56-04:00`
			`draft: false`
Medium syndication information 2023-01-05 14:04:45 -05:00			`medium_enabled: true`
Website snapshot 2020-01-15 21:51:49 -05:00			`---`

			`One of the greatest benefits I believe of integrating Gitlab's CI/CD into your workload is code linting and building. This immediately eliminates the easy mistakes that developers make and wastes less people's time.`

			I'm working towards getting the build setup just right in one of the projects I'm currently working. However, in the meantime, Gitlab supports running it's CI/CD jobs under the `shell executor`. I would like to go to the default Docker route in the future once I figure out all of the dependencies of the project I'm building.