Skip to content
Latchkey

Doc Build workflow (dromara/domain-admin)

The Doc Build workflow from dromara/domain-admin, explained and optimized by Latchkey.

F

CI health: F - at risk

Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: dromara/domain-admin.github/workflows/doc-build.ymlLicense MITView source

What it does

This is the Doc Build workflow from the dromara/domain-admin repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

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

The workflow

workflow (.yml)
# https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml
name: Doc Build

on:
  push:
    branch: ['master']

permissions:
  contents: write

jobs:
  deploy:

    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Set up Python
        uses: actions/setup-python@v3
        with:
          python-version: '3.8'

      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install -r doc/requirements.txt

      - name: Build and publish
        run: |
            cd ./doc && make html && cd ../

      - name: Deploy 🚀
        uses: JamesIves/github-pages-deploy-action@4.1.1
        with:
          branch: doc # The branch the action should deploy to.
          folder: doc/build/html # The folder the action should deploy.

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

# https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml
name: Doc Build
 
on:
  push:
    branch: ['master']
 
permissions:
  contents: write
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  deploy:
    timeout-minutes: 30
 
    runs-on: latchkey-small
 
    steps:
      - name: Checkout
        uses: actions/checkout@v3
 
      - name: Set up Python
        uses: actions/setup-python@v3
        with:
          cache: 'pip'
          python-version: '3.8'
 
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install -r doc/requirements.txt
 
      - name: Build and publish
        run: |
            cd ./doc && make html && cd ../
 
      - name: Deploy 🚀
        uses: JamesIves/github-pages-deploy-action@4.1.1
        with:
          branch: doc # The branch the action should deploy to.
          folder: doc/build/html # The folder the action should deploy.
 

What changed

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.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

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

Actions used in this workflow