如何避免GitLab CI/CD在新建与main无差异分支时执行流水线

问题原因 #

你当前的only: changes逻辑默认和上一次提交做对比，但从main分支新建分支并首次推送时，CI会将新分支的初始提交与空仓库对比，自然判定所有文件夹都有变更，从而触发全部任务。要实现需求，必须明确指定和main分支做变更对比。

修改后的YAML配置 #

folder-a:
  tags:
    - main-runner
  stage: build-a
  script:
    - echo "folder-a"
  rules:
    - if: '$CI_PIPELINE_SOURCE == "push"'
      changes:
        - a/**
      compare_to: main
      when: always

folder-b:
  tags:
    - main-runner
  stage: build-b
  script:
    - echo "folder-b"
  rules:
    - if: '$CI_PIPELINE_SOURCE == "push"'
      changes:
        - b/**
      compare_to: main
      when: always

配置说明 #

• 用rules替代only，更灵活控制流水线触发逻辑
• compare_to: main强制CI对比当前分支与main分支的变更，而非默认的上一次提交
• if: '$CI_PIPELINE_SOURCE == "push"'限定仅在推送代码时应用该规则（可根据实际场景调整，比如合并请求触发等）
• 当新分支与main分支完全一致时，两个任务的changes条件均不满足，流水线不会触发；若有变更，仅对应变更文件夹的任务会执行

兼容方案（针对不支持compare_to的CI系统） #

如果你的CI平台不支持compare_to参数，可通过脚本手动对比变更：

folder-a:
  tags:
    - main-runner
  stage: build-a
  script:
    - echo "folder-a"
  rules:
    - if: '$CI_PIPELINE_SOURCE == "push"'
      when: always
  before_script:
    - git fetch origin main
    - CHANGES=$(git diff --name-only origin/main HEAD | grep "^a/")
    - if [ -z "$CHANGES" ]; then exit 1; fi

folder-b:
  tags:
    - main-runner
  stage: build-b
  script:
    - echo "folder-b"
  rules:
    - if: '$CI_PIPELINE_SOURCE == "push"'
      when: always
  before_script:
    - git fetch origin main
    - CHANGES=$(git diff --name-only origin/main HEAD | grep "^b/")
    - if [ -z "$CHANGES" ]; then exit 1; fi

该方案通过git diff手动检查当前分支与main分支的目录变更，若无对应目录的变更则直接退出任务，避免不必要的执行。

内容的提问来源于stack exchange，提问作者manasvb