Building a CI pipeline might sound bombastic, but with Gitlab CI we can do it in a few minutes. At Nielsen, we had a CI/CD process running in Jenkins and we’ve decided to migrate it over to Gitlab CI.
In this post I’ll summarise why we did it and how easily you can do it too.
Let’s start by understanding the two main keywords:
CI stands for Continuous Integration. In most companies, there are multiple teams working together and pushing new features constantly. The idea behind this concept is to enable every team to write code and push features. …
As an infrastructure team, we support multiple web application teams in our company. All requests made in the system are passed via our infrastructure. This means we are responsible for authorization, authentication, and many more. This gives our application teams the advantage of focusing simply on developing their own application.
Hence, we need to support multiple functionalities, one of which was to support file uploading and downloading. Until recently, we only supported sending files via API with the usage of a buffer. …
Testing is very important to us. We write a lot of tests and make sure we never publish code without testing. Recently as part of our constant effort to improve our testing abilities, we decided to migrate from Tape to Jest in our Node projects.
The process was fairly smooth, but we did have a few bumps in the road.
In this post, I will share some insights about those “bumps,” so your ride can be even smoother.
I will focus on or insights and will not give a full introduction to Jest. You can check out the official documentation…