Build workflow (gardener/gardener)

The Build workflow from gardener/gardener, explained and optimized by Latchkey.

What it does

This is the Build workflow from the gardener/gardener repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: Build
on:
  push:
    branches:
      - master
      - 'release-v*'

jobs:
  build:
    if: ${{ github.repository == 'gardener/gardener' }}
    uses: ./.github/workflows/build.yaml
    with:
      mode: snapshot
    secrets: inherit
    permissions:
      contents: read
      packages: write
      id-token: write

  component-descriptor:
    if: ${{ github.repository == 'gardener/gardener' }}
    uses: gardener/cc-utils/.github/workflows/post-build.yaml@v1
    needs:
      - build
    permissions:
      id-token: write
      contents: write

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Build
on:
  push:
    branches:
      - master
      - 'release-v*'
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    if: ${{ github.repository == 'gardener/gardener' }}
    uses: ./.github/workflows/build.yaml
    with:
      mode: snapshot
    secrets: inherit
    permissions:
      contents: read
      packages: write
      id-token: write
 
  component-descriptor:
    timeout-minutes: 30
    if: ${{ github.repository == 'gardener/gardener' }}
    uses: gardener/cc-utils/.github/workflows/post-build.yaml@v1
    needs:
      - build
    permissions:
      id-token: write
      contents: write
 

What changed

• Cancel superseded runs when a branch or PR gets a newer push.
• Add a job timeout so a hung step cannot burn hours of runner time.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

This workflow runs 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.