Running CI/CD Pipeline with GitLab CI

GitLab allows us to deploy CI/CD pipeline runners on our own resources within our environment. This option is available not only for the self-hosted plan but also for the cloud service plan (gitlab.com). With this setup, unlike GitHub Action, we can avoid incurring additional costs for extended pipeline runtime. This is because we can deploy the runner on an on-demand server and optimize its usage.

GitLab CI offers several options for setting up resources to run CI/CD pipelines. A runner can be configured to handle jobs for specific groups or projects using designated tags. It can also be set to use different executors, such as Shell, Docker, Kubernetes, or VirtualBox. A comparison table of the supported executors is available in the executor documentation. Some executors offer greater flexibility and ease of use, while others may be more rigid but enhance server security.

Installing the runner in our machine

For example, we will deploy the runner on an Ubuntu server. It is recommended to use a separate machine from the one hosting the GitLab server. Detailed instructions can be found in the runner documentation.

curl -L "https://packages.gitlab.com/install/repositories/runner/gitlab-runner/script.deb.sh" | sudo bash
sudo apt-get install gitlab-runner

Additionally, we have to install Docker because we will use it as the executor in this process.

Registering the runner on our GitLab

We will configure the runner to handle jobs only from a specific group using designated tags. In this example, I use the latest registration mechanism available in GitLab Runner 15.10 or later.

Visit the control panel of the desired group and choose the Build > Runners menu.
Choose the "New group runner" option.
Fill in the required fields including the tags field.
Copy the command generated after submitting the form that contains the registration token.

Linking the runner with the GitLab CI instance

Next, return to the machine where the runner is installed and run the command generated in the previous step. The command will look like the example below.

gitlab-runner register --url https://YOUR_GITLAB_HOST --token glrt-xxx

When running the command, you will be prompted to answer a few questions. For the executor, you can type "docker", and for the default image, you can select "ubuntu:22.04". Detailed instructions for registering the runner are available in the runner configuration documentation.

Configuring the runner

Before the runner can function properly, we need to update certain values in the configuration file located at "/etc/gitlab-runner/config.toml". First, generate a Personal Access Token or a group-level token to allow the runner to pull the contents of the repository in the group. Then, input the token value into the configuration as shown in the example below.

[[runners]]
  name = "something"
  # ...
  executor = "docker"
  clone_url = "https://gitlab-ci-token:YOUR_PAT_OR_GROUP_TOKEN@YOUR_GITLAB_HOST"
  # ...
  [runners.docker]
    image = "ubuntu:22.04"
    pull_policy = "if-not-present"

Lastly, we must restart the runner with this command: gitlab-runner restart.

Configuring the CI/CD pipeline in our project

In GitLab CI, the pipeline script is stored in the ".gitlab-ci.yml" file within the project repository. Since the runner is configured to handle jobs with specific tags, each job in the pipeline script must be assigned the appropriate tag, as shown in the example below.

stages:
  - build
  - deploy

build-job:
  tags:
    - YOUR_TAG
  stage: build
  script:
    - echo "Compile complete."

deploy-job:
  tags:
    - YOUR_TAG
  stage: deploy
  script:
    - echo "Application successfully deployed."

After we push the update, we can check the status on the "Build > Pipelines" menu in our project repository.

Comments

Deliver SaaS According Twelve-Factor App

If you haven't heard of the twelve-factor app , it gives us a recommendation or a methodology for developing SaaS or web apps structured into twelve items. The recommendation has some connections with microservice architecture and cloud-native environments which become more popular today. We can learn the details on its website . In this post, we will do a quick review of the twelve points. One Codebase Multiple Deployment We should maintain only one codebase for our application even though the application may be deployed into multiple environments like development, staging, and production. Having multiple codebases will lead to any kinds of complicated issues. Explicitly State Dependencies All the dependencies for running our application should be stated in the project itself. Many programming languages have a kind of file that maintains a list of the dependencies like package.json in Node.js. We should also be aware of the dependencies related to the pla...

Configuring Swap Memory on Ubuntu Using Ansible

If we maintain a Linux machine with a low memory capacity while we are required to run an application with high memory consumption, enabling swap memory is an option. Ansible can be utilized as a helper tool to automate the creation of swap memory. A swap file can be allocated in the available storage of the machine. The swap file then can be assigned as a swap memory. Firstly, we should prepare the inventory file. The following snippet is an example, you must provide your own configuration. [server] 192.168.1.2 [server:vars] ansible_user=root ansible_ssh_private_key_file=~/.ssh/id_rsa Secondly, we need to prepare the task file that contains not only the tasks but also some variables and connection information. For instance, we set /swapfile as the name of our swap file. We also set the swap memory size to 2GB and the swappiness level to 60. - hosts: server become: true vars: swap_vars: size: 2G swappiness: 60 For simplicity, we only check the...

Rangkaian Sensor Infrared dengan Photo Dioda

Keunggulan photodioda dibandingkan LDR adalah photodioda lebih tidak rentan terhadap noise karena hanya menerima sinar infrared, sedangkan LDR menerima seluruh cahaya yang ada termasuk infrared. Rangkaian yang akan kita gunakan adalah seperti gambar di bawah ini. Pada saat intensitas Infrared yang diterima Photodiode besar maka tahanan Photodiode menjadi kecil, sedangkan jika intensitas Infrared yang diterima Photodiode kecil maka tahanan yang dimiliki photodiode besar. Jika tahanan photodiode kecil maka tegangan V- akan kecil . Misal tahanan photodiode mengecil menjadi 10kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 10 / (10+10) x Vcc V- = (1/2) x 5 Volt V- = 2.5 Volt Sedangkan jika tahanan photodiode besar maka tegangan V- akan besar (mendekati nilai Vcc). Misal tahanan photodiode menjadi 150kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 150 / (1...

Deploying a Web Server on UpCloud using Terraform Modules

In my earlier post , I shared an example of deploying UpCloud infrastructure using Terraform from scratch. In this post, I want to share how to deploy the infrastructure using available Terraform modules to speed up the set-up process, especially for common use cases like preparing a web server. For instance, our need is to deploy a website with some conditions as follows. The website can be accessed through HTTPS. If the request is HTTP, it will be redirected to HTTPS. There are 2 domains, web1.yourdomain.com and web2.yourdomain.com . But, users should be redirected to "web2" if they are visiting "web1". There are 4 main modules that we need to set up the environment. Private network. It allows the load balancer to connect with the server and pass the traffic. Server. It is used to host the website. Load balancer. It includes backend and frontend configuration. Dynamic certificate. It is requ...

Armin and Eren VS Colossal Titan

The trick was unexpected and caught Bertolt off guard.

Manage Kubernetes Cluster using Rancher

Recently, I sought a simpler method to deploy and maintain Kubernetes clusters across various cloud providers. The goal was to use it for development purposes with the ability to manage the infrastructure and costs effortlessly. After exploring several options, I decided to experiment with Rancher. Rancher offers a comprehensive software stack for teams implementing container technology. It tackles both the operational and security hurdles associated with managing numerous Kubernetes clusters. Additionally, it equips DevOps teams with integrated tools essential for managing containerized workloads. Rancher also offers an open-source version, allowing free deployment within one's infrastructure. The Rancher platform can be deployed either as a Docker container or within a Kubernetes cluster utilizing the K3s engine. We can read the documentation on how to install Rancher on K3s using Helm . Rancher itself enables the creation and provisioning of Kubernetes clusters and ...

LUKI NOTES

Search This Blog