Github Actions vs. Jenkins

In the age of cloud computing and devops, deploying your application several times a day is considered business as usual. But, in order to make sure your latest updates don’t break any previous features, it is necessary to build and test your code before deploying. Doing all of this work manually several times a day can get quite tedious. That’s why the concept of CICD was introduced, and has since become the industry standard for deploying new versions of software.

What is CICD?

CICD stands for Continuous Integration Continuous Deployment, which is a fancy term for automating your deployments, so that they take significantly less time, and are immune to human errors that appear very often when deploying manually. Each CICD workflow consists of a pipeline, which is just a set of stages/jobs that need to be performed successfully before the new version of the software is released in production. These stages are split into smaller bits, called steps, which are the explicit commands that our CICD pipeline executes. The three main stages of a CICD pipeline are usually:

Build, Test and Deploy

The build stage builds the code, meaning it compiles it into a format that is executable, either directly on the machine, or by some sort of virtual machine/interpreter. The build stage can also build a Docker image out of the…