Gitlab CI 小试牛刀

站长

2022年12月06日 08:59 · 阅读数 19

前言

前端工程化中 CI 是必不可少的一环，大家的团队中或多或少都有不同的 CI 能力，有的可能由运维同学使用 JIRA 配置（前司），更多的相信已经迁移到 Gitlab 到 CI/CD 中。那么今天就来聊聊什么是 CI 以及如何在 Gitlab 中配置 CI 能力。

CI

CI(continuous integration) 持续集成是将所有代码更改尽早并经常集成到共享源代码存储库的主分支中的做法，在您提交或合并它们时自动测试每个更改，并自动启动构建。通过持续集成，可以更轻松地在软件开发生命周期中更早地识别和修复错误和安全问题。通过频繁合并更改并触发自动测试和验证过程，您可以最大限度地减少代码冲突的可能性，即使有多个开发人员在同一个应用程序上工作。第二个优点是您不必等待很长时间才能获得答案，并且可以在必要时修复错误和安全问题，同时您还记得这个主题。常见的代码验证过程从验证代码质量的静态代码分析开始。一旦代码通过静态测试，自动化 CI 例程就会打包并编译代码以进行进一步的自动化测试。 CI 流程应该有一个版本控制系统来跟踪更改，因此您知道所使用代码的版本。

简单点说，CI 就是对你某个版本的代码进行自动化的检查，比如代码格式，单元测试等等，让当前版本的代码保持在持续稳定的可用状态。

Gitlab CI配置

我们来看看如何从 0 开始配置 Gitlab 的 CI

前提：你已经在 Gitlab 有个项目

1. 在项目根文件上添加 .gtilab-ci.yml 文件

我们看看 Gitlab 默认生成的示例文件

# This file is a template, and might need editing before it works on your project.
# This is a sample GitLab CI/CD configuration file that should run without any modifications.
# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
# it uses echo commands to simulate the pipeline execution.
#
# A pipeline is composed of independent jobs that run scripts, grouped into stages.
# Stages run in sequential order, but jobs within stages run in parallel.
#
# For more information, see: https://docs.gitlab.com/ee/ci/yaml/index.html#stages
#
# You can copy and paste this template into a new `.gitlab-ci.yml` file.
# You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword.
#
# To contribute improvements to CI/CD templates, please follow the Development guide at:
# https://docs.gitlab.com/ee/development/cicd/templates.html
# This specific template is located at:
# https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Getting-Started.gitlab-ci.yml

stages:          # List of stages for jobs, and their order of execution
  - build
  - test
  - deploy

build-job:       # This job runs in the build stage, which runs first.
  stage: build
  tags:
    - xxx
  script:
    - echo "Compiling the code..."
    - echo "Compile complete."

unit-test-job:   # This job runs in the test stage.
  stage: test    # It only starts when the job in the build stage completes successfully.
  script:
    - echo "Running unit tests... This will take about 60 seconds."
    - sleep 60
    - echo "Code coverage is 90%"

lint-test-job:   # This job also runs in the test stage.
  stage: test    # It can run at the same time as unit-test-job (in parallel).
  script:
    - echo "Linting code... This will take about 10 seconds."
    - sleep 10
    - echo "No lint issues found."

deploy-job:      # This job runs in the deploy stage.
  stage: deploy  # It only runs when *both* jobs in the test stage complete successfully.
  script:
    - echo "Deploying application..."
    - echo "Application successfully deployed."