GitLab流水线问题：调度触发含手动任务的实现方案咨询

这个问题在GitLab流水线实践里挺常见的，核心是手动触发任务和调度触发任务的依赖绑定冲突，我给你两个直接可行的解决方案：

方案1：合并任务，用rules区分触发场景 #

把FirstJob和FirstJobSchedule合并成一个任务，通过GitLab内置的CI_PIPELINE_SOURCE环境变量判断触发来源，分别执行对应逻辑，同时设置不同的执行条件。这样AC-test只需要依赖这一个任务，不管是手动还是调度触发都能正常流转：

stages:
  - firstjob
  - test
  - build
  - deploy

FirstJob:
  stage: firstjob
  script:
    - |
      # 根据触发来源执行不同逻辑
      if [[ "$CI_PIPELINE_SOURCE" == "schedule" ]]; then
        echo "Hello Scheduled Peoples!"
      else
        echo "Hello Peoples!"
      fi
    - sleep 1
  rules:
    # 调度触发时自动执行
    - if: '$CI_PIPELINE_SOURCE == "schedule"'
      when: always
    # 手动/触发按钮触发时需要手动确认
    - if: '$CI_PIPELINE_SOURCE == "web" || $CI_PIPELINE_SOURCE == "trigger"'
      when: manual
  allow_failure: false

AC-test:
  needs: [FirstJob]
  stage: test
  script:
    - echo "AC Test is running"
    - sleep 10

ProdJobBuild:
  stage: build
  needs: [AC-test]
  script:
    - echo "Building thing to prod"

ProdJobDeploy:
  stage: deploy
  needs: [ProdJobBuild]
  script:
    - echo "Deploying thing to prod"

这个方案是GitLab官方推荐的做法，用rules替代老旧的only/except，逻辑更清晰，也避免了重复定义任务。

方案2：给AC-test设置动态依赖 #

如果你不想合并两个任务，可以让AC-test根据触发来源动态选择依赖的前置任务，同样用rules实现：

stages:
  - firstjob
  - test
  - build
  - deploy

FirstJob:
  stage: firstjob
  script:
    - echo "Hello Peoples!"
    - sleep 1
  when: manual
  allow_failure: false

FirstJobSchedule:
  stage: firstjob
  script:
    - echo "Hello Scheduled Peoples!"
    - sleep 1
  only:
    - schedule
  allow_failure: false

AC-test:
  stage: test
  script:
    - echo "AC Test is running"
    - sleep 10
  rules:
    # 调度触发时依赖FirstJobSchedule
    - if: '$CI_PIPELINE_SOURCE == "schedule"'
      needs: [FirstJobSchedule]
    # 手动触发时依赖FirstJob
    - if: '$CI_PIPELINE_SOURCE == "web" || $CI_PIPELINE_SOURCE == "trigger"'
      needs: [FirstJob]

ProdJobBuild:
  stage: build
  needs: [AC-test]
  script:
    - echo "Building thing to prod"

ProdJobDeploy:
  stage: deploy
  needs: [ProdJobBuild]
  script:
    - echo "Deploying thing to prod"

这个方案保留了原有两个任务的独立性，适合任务逻辑差异较大的场景。

补充说明 #

确实有很多GitLab用户遇到过类似的问题，本质都是手动任务的when: manual配置和调度触发的自动执行需求冲突，通过rules做条件判断是最通用的解决思路，它能让流水线根据不同触发场景灵活调整执行逻辑。

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