GitLab CI extends继承脚本无输出问题排查求助

核心问题原因 #

GitLab CI 的作业继承规则里，子作业直接定义script字段时，会完全覆盖父模板中的script内容，不会自动合并。你看到的现象就是因为build-publish:android_qa和build-publish:android_prod里的script覆盖了.build-publish:android、.download-signin-keystore等模板的脚本，导致继承的代码根本没执行，自然没有输出。

解决方案 #

方法1：用!reference关键字合并脚本 #

GitLab CI 支持通过!reference引用模板中的脚本片段，实现脚本的追加而非覆盖。修改你的子作业配置：

build-publish:android_qa:
  stage: qa_release
  extends:
    - .build-publish:android
    - .deploy-job
  variables:
    SECURE_FILES_DOWNLOAD_PATH: ${CI_PROJECT_DIR}/android/app
    SOK_BUILD_ENV: 'qa'
  script:
    # 依次引用各模板的脚本
    - !reference [.download-signin-keystore, script]
    - !reference [.build-publish:android, script]
    - !reference [.deploy-job, script]
    - echo "android_qa"  # 自定义脚本
  needs:
    - test
  environment:
      name: qa/android
      deployment_tier: staging

build-publish:android_prod:
  stage: prod_release
  variables:
    SOK_BUILD_ENV: 'prod'
  extends:
    - .build-publish:android
    - .deploy-job
  script:
    - !reference [.download-signin-keystore, script]
    - !reference [.build-publish:android, script]
    - !reference [.deploy-job, script]
    - echo "prod" # 自定义脚本
  needs:
    - test
  environment:
      name: prod/android
      deployment_tier: staging

方法2：拆分脚本为可复用锚点 #

如果需要更灵活的复用，可以把脚本拆成单独的锚点片段，避免重复引用：

# 定义可复用的脚本锚点
.download-keystore-script: &download-keystore-script
  - curl --silent "https://gitlab.com/gitlab-org/incubation-engineering/mobile-devops/download-secure-files/-/raw/main/installer" | bash
  - ls -lah ${CI_PROJECT_DIR}/android/app

.build-android-script: &build-android-script
  - echo "Build env $SOK_BUILD_ENV"
  - echo "hello wolrd"

.deploy-script: &deploy-script
  - echo "'Deploy to Environment'"

# 修改模板使用锚点
.download-signin-keystore:
  image: docker:latest
  before_script:
    - apk add --update curl && rm -rf /var/cache/apk/*
    - apk add bash
  variables:
    SECURE_FILES_DOWNLOAD_PATH: ${CI_PROJECT_DIR}/android/app
  script: *download-keystore-script
  after_script:
     - rm -f ${CI_PROJECT_DIR}/android/app/signing_keystore_password.keystore

.build-publish:android:
  stage: build-publish
  extends: .gradle-job
  script: *build-android-script

.deploy-job:
  script: *deploy-script
  rules:
    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
      when: never
    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
      when: manual

# 子作业直接组合锚点脚本
build-publish:android_qa:
  stage: qa_release
  extends:
    - .build-publish:android
    - .deploy-job
    - .download-signin-keystore
  variables:
    SECURE_FILES_DOWNLOAD_PATH: ${CI_PROJECT_DIR}/android/app
    SOK_BUILD_ENV: 'qa'
  script:
    - *download-keystore-script
    - *build-android-script
    - *deploy-script
    - echo "android_qa"
  needs:
    - test
  environment:
      name: qa/android
      deployment_tier: staging

排查步骤 #

• 确认最终配置：在GitLab项目的CI/CD > Pipelines页面，点击对应流水线的View yaml，查看作业最终生成的配置，确认script是否被覆盖。
• 检查执行触发条件：查看.deploy-job的rules，确认作业是否满足执行条件（比如是否是默认分支、是否手动触发）。
• 查看完整日志：进入作业的日志页面，检查是否有Skipping script等提示，同时确认before_script是否正常执行，排除前置步骤失败导致脚本未运行的情况。
• 单模板测试：创建临时测试作业，只继承单个模板（比如只继承.download-signin-keystore），验证脚本是否有输出，逐步定位问题模板。

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