如何在GitLab CI中基于Ansible Playbook变更触发合并请求

针对你的需求，这里提供两种无需解析Ansible PLAY RECAP的可靠实现方案，核心通过Git文件追踪或Ansible预检测来判断是否触发合并请求：

方案一：Git文件变更检测（推荐） #

直接通过Git追踪生成的inventory文件状态，这是最准确的变更判断方式，完全规避解析Playbook输出的不可靠性。

修改后的.gitlab-ci.yaml配置：

include:
  - local: .gitlab-ci-vars.yml

image: 
  name: $ANSIBLE_IMAGE
before_script:
  - ansible --version
  # 初始化Git配置，确保能正常检测文件变更
  - git config --global user.name "GitLab CI/CD"
  - git config --global user.email "ci@your-domain.com"

stages:
  - "inventory build"
  - create_merge_request

inventory-build:
  stage: inventory build
  script:
    - ansible-playbook $PLAYBOOK_NAME
    # 检查目标inventory文件是否有变更，将结果写入环境变量文件
    - |
      INVENTORY_PATH="path/to/your/inventory.file"
      if git diff --name-only | grep -q "^${INVENTORY_PATH}$"; then
        echo "INVENTORY_CHANGED=true" >> variables.env
        git add "${INVENTORY_PATH}"
        git commit -m "Auto-update inventory [CI]"
        git push origin $CI_COMMIT_BRANCH
      else
        echo "INVENTORY_CHANGED=false" >> variables.env
      fi
  tags:
    - $RUNNER_TAG
  # 将变量传递给后续作业
  artifacts:
    reports:
      dotenv: variables.env

create_merge_request:
  stage: create_merge_request
  # 仅当inventory有变更时执行
  rules:
    - if: $INVENTORY_CHANGED == "true"
  script:
    - echo "Creating merge request..."
    # 示例：用GitLab CLI创建MR（需提前安装glab）
    - glab mr create --source-branch $CI_COMMIT_BRANCH --target-branch main --title "Auto-update inventory file" --description "Generated by CI after inventory changes"
    # 或用GitLab API创建（需配置GITLAB_TOKEN变量）
    # curl --request POST --header "PRIVATE-TOKEN: $GITLAB_TOKEN" "$CI_API_V4_URL/projects/$CI_PROJECT_ID/merge_requests" --form "source_branch=$CI_COMMIT_BRANCH" --form "target_branch=main" --form "title=Auto-update inventory file"
  tags:
    - $RUNNER_TAG

方案二：Ansible预检测变更 #

利用Ansible的--check模式提前判断执行Playbook是否会产生变更，再决定是否执行后续流程：

include:
  - local: .gitlab-ci-vars.yml

image: 
  name: $ANSIBLE_IMAGE
before_script:
  - ansible --version

stages:
  - "check inventory changes"
  - "inventory build"
  - create_merge_request

check-inventory-changes:
  stage: "check inventory changes"
  script:
    - |
      # 用--check模式执行Playbook，统计会变更的任务数
      CHANGE_COUNT=$(ansible-playbook $PLAYBOOK_NAME --check | grep -c "changed=")
      if [ $CHANGE_COUNT -gt 0 ]; then
        echo "INVENTORY_WILL_CHANGE=true" >> variables.env
      else
        echo "INVENTORY_WILL_CHANGE=false" >> variables.env
      fi
  artifacts:
    reports:
      dotenv: variables.env
  tags:
    - $RUNNER_TAG

inventory-build:
  stage: inventory build
  rules:
    - if: $INVENTORY_WILL_CHANGE == "true"
  script:
    - ansible-playbook $PLAYBOOK_NAME
    - git add path/to/your/inventory.file
    - git commit -m "Auto-update inventory [CI]"
    - git push origin $CI_COMMIT_BRANCH
  tags:
    - $RUNNER_TAG

create_merge_request:
  stage: create_merge_request
  rules:
    - if: $INVENTORY_WILL_CHANGE == "true"
  script:
    - echo "Creating merge request..."
    # 同方案一的MR创建命令
  tags:
    - $RUNNER_TAG

关键注意事项 #

• Git权限：确保CI运行器拥有仓库的推送权限，可通过项目设置中的CI/CD变量配置GITLAB_TOKEN（需包含api和write_repository权限）。
• 变量传递：使用artifacts:reports:dotenv是GitLab 16.x版本中跨作业传递变量的官方可靠方式。
• 路径准确性：替换配置中的path/to/your/inventory.file为实际的inventory文件路径。

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