Documentation Build workflow (samsledje/D-SCRIPT)
The Documentation Build workflow from samsledje/D-SCRIPT, explained and optimized by Latchkey.
CI health: D - needs work
Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Documentation Build workflow from the samsledje/D-SCRIPT 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
name: Documentation Build
on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]
# Allow manual triggering
workflow_dispatch:
permissions:
contents: read
jobs:
docs-build:
runs-on: ubuntu-22.04
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Set up Python 3.11
uses: actions/setup-python@v4
with:
python-version: "3.11"
- name: Install dependencies
run: |
python -m pip install --upgrade pip
pip install -e ".[docs]"
- name: Build documentation
working-directory: docs
run: |
# Build HTML documentation with warnings treated as errors
sphinx-build -W -b html source build/html
- name: Check for build artifacts
run: |
# Verify that the documentation was built successfully
if [ ! -f "docs/build/html/index.html" ]; then
echo "Error: Documentation build failed - index.html not found"
exit 1
fi
echo "Documentation build completed successfully"
- name: Upload documentation artifacts
uses: actions/upload-artifact@v4
if: always()
with:
name: documentation-html
path: docs/build/html/
retention-days: 30
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.
name: Documentation Build on: push: branches: [ "main" ] pull_request: branches: [ "main" ] # Allow manual triggering workflow_dispatch: permissions: contents: read concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: docs-build: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Checkout repository uses: actions/checkout@v4 - name: Set up Python 3.11 uses: actions/setup-python@v4 with: cache: 'pip' python-version: "3.11" - name: Install dependencies run: | python -m pip install --upgrade pip pip install -e ".[docs]" - name: Build documentation working-directory: docs run: | # Build HTML documentation with warnings treated as errors sphinx-build -W -b html source build/html - name: Check for build artifacts run: | # Verify that the documentation was built successfully if [ ! -f "docs/build/html/index.html" ]; then echo "Error: Documentation build failed - index.html not found" exit 1 fi echo "Documentation build completed successfully" - name: Upload documentation artifacts uses: actions/upload-artifact@v4 if: always() with: name: documentation-html path: docs/build/html/ retention-days: 30
What changed
- Run on Latchkey managed runners with one line (
runs-on), which apply the fixes below automatically and self-heal transient failures. This example useslatchkey-small; pick the runner size that fits the job. - Cancel superseded runs when a branch or PR gets a newer push.
- Cache dependency installs on the setup step so they are served from cache.
- Add a job timeout so a hung step cannot burn hours of runner time.
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:
- Dependency installs
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.