For simplicity, let's consider Docker as an executor for all runners.Įach job starts with a clean slate and doesn't know the results of the previous one. The GitLab-runner is the agent that can run jobs. When we start a Pipeline, a random runner with free resources executes the needed job. Jobs work on a distributed farm of runners. The Pipeline is a set of stages and each stage can have one or more jobs. Let's see what the Pipeline in GitLab terms means. GitLab has bright documentation, but the Node.js app with cache example and the Pipeline template for Node.js contradict each other. People are confused when they have to choose between cache and artifacts. Cache and artifacts to the rescue! They help reduce the time it takes to run a Pipeline drastically. Nobody wants to wait for the CI completion too much, it's better to set up all the tweaks to avoid long waiting between the commit the build status. There are three things you can watch forever: fire burning, water falling, and the build is passing after your next commit. I'll show how to configure the Pipeline for the Node.js app in a pragmatic way to achieve good performance and resource utilization. Let's discuss the difference between GitLab cache and artifacts. Apart from web services testing, I maintain CI/CD Pipelines in our team's GitLab. Hi, DEV Community! I've been working in the software testing field for more than eight years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |