如何在GitHub Action中避免多Workflow触发时重复执行构建镜像等任务？

针对你遇到的多Workflow重复构建镜像的问题，有几种实用方案可以实现所有依赖任务共享同一个构建结果：

1. 单一核心Workflow+事件触发依赖Workflow #

不要让多个Workflow直接监听push事件，而是只保留一个核心Workflow负责构建镜像，完成后通过事件触发其他需要该镜像的Workflow，从根源避免重复构建：

• 核心构建Workflow（build-shared-image.yml）：

  name: Build Shared Docker Image
  on: [push]
  jobs:
    build-and-push:
      runs-on: ubuntu-latest
      steps:
        - uses: actions/checkout@v4
        - name: 登录GitHub Packages
          uses: docker/login-action@v3
          with:
            registry: ghcr.io
            username: ${{ github.actor }}
            password: ${{ secrets.GITHUB_TOKEN }}
        - name: 构建并推送镜像
          uses: docker/build-push-action@v5
          with:
            context: .
            push: true
            tags: ghcr.io/${{ github.repository }}/my-app:${{ github.sha }}
        - name: 触发依赖Workflow
          uses: peter-evans/repository-dispatch@v3
          with:
            token: ${{ secrets.PAT_TOKEN }}
            event-type: shared-image-ready
            client-payload: '{"image_tag": "${{ github.sha }}"}'
  

• 依赖Workflow（比如integration-test.yml）：

  name: Integration Test
  on:
    repository_dispatch:
      types: [shared-image-ready]
  jobs:
    run-tests:
      runs-on: ubuntu-latest
      steps:
        - name: 登录GitHub Packages
          uses: docker/login-action@v3
          with:
            registry: ghcr.io
            username: ${{ github.actor }}
            password: ${{ secrets.GITHUB_TOKEN }}
        - name: 拉取共享镜像
          run: docker pull ghcr.io/${{ github.repository }}/my-app:${{ github.event.client_payload.image_tag }}
        - name: 执行集成测试
          run: docker run ghcr.io/${{ github.repository }}/my-app:${{ github.event.client_payload.image_tag }} npm run test:integration
  

2. 跨Workflow使用needs关键字 #

如果你的多个Workflow都监听push事件，可以让它们直接依赖核心构建Workflow的执行结果，确保只有构建完成后才会运行后续任务：

• 核心构建Workflow（build-image.yml）：

  name: Build Docker Image
  on: [push]
  jobs:
    build:
      runs-on: ubuntu-latest
      outputs:
        image_tag: ${{ steps.build.outputs.tag }}
      steps:
        - uses: actions/checkout@v4
        - name: 构建镜像
          id: build
          run: |
            TAG="my-app:${{ github.sha }}"
            docker build -t $TAG .
            echo "tag=$TAG" >> $GITHUB_OUTPUT
  

• 依赖Workflow（比如api-test.yml）：

  name: API Integration Test
  on: [push]
  needs: build-image
  jobs:
    test:
      runs-on: ubuntu-latest
      steps:
        - name: 使用共享镜像
          run: docker run ${{ needs.build-image.outputs.image_tag }} npm run test:api
  

  注意：这种方式要求所有Workflow在同一次push事件下触发，且核心Workflow名称要完全匹配；如果核心Workflow失败，依赖的Workflow会直接跳过。

3. 可复用Workflow+镜像缓存优化 #

如果坚持使用可复用Workflow，可以通过缓存镜像层彻底减少重复构建的时间成本：

# 可复用Workflow（.github/workflows/reusable-build.yml）
name: Reusable Docker Build
on:
  workflow_call:
    outputs:
      image_tag:
        description: "构建好的镜像标签"
        value: ${{ jobs.build.outputs.image_tag }}

jobs:
  build:
    runs-on: ubuntu-latest
    outputs:
      image_tag: ${{ steps.build.outputs.tag }}
    steps:
      - uses: actions/checkout@v4
      - name: 缓存Docker镜像层
        uses: actions/cache@v3
        with:
          path: /tmp/.buildx-cache
          key: ${{ runner.os }}-buildx-${{ github.sha }}
          restore-keys: |
            ${{ runner.os }}-buildx-
      - name: 构建镜像
        id: build
        uses: docker/build-push-action@v5
        with:
          context: .
          push: false
          load: true
          tags: my-app:${{ github.sha }}
          cache-from: type=local,src=/tmp/.buildx-cache
          cache-to: type=local,dest=/tmp/.buildx-cache,mode=max
      - name: 输出镜像标签
        run: echo "tag=my-app:${{ github.sha }}" >> $GITHUB_OUTPUT

后续调用这个可复用Workflow时，会优先使用缓存的镜像层，几乎等同于直接复用之前的构建结果。

内容的提问来源于stack exchange，提问作者Kane.Sun