SDK CI workflow (GACWR/OpenUBA)
The SDK CI workflow from GACWR/OpenUBA, 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 SDK CI workflow from the GACWR/OpenUBA 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: SDK CI
on:
push:
branches: [master, dev/**]
paths:
- "sdk/**"
pull_request:
branches: [master]
jobs:
build:
name: Build & verify (Python ${{ matrix.python-version }})
runs-on: ubuntu-latest
strategy:
matrix:
python-version: ["3.9", "3.12", "3.13"]
steps:
- uses: actions/checkout@v4
- name: Set up Python ${{ matrix.python-version }}
uses: actions/setup-python@v5
with:
python-version: ${{ matrix.python-version }}
- name: Install build tools
run: python -m pip install --upgrade pip build
- name: Build package
working-directory: sdk
run: |
rm -rf dist/
python -m build
- name: Install from built wheel
run: pip install sdk/dist/*.whl
- name: Verify CLI entry point
run: openuba --help
- name: Verify Python imports
run: |
python -c "import openuba; print(f'openuba version: {openuba.__version__}')"
python -c "from openuba.client import OpenUBAClient; print('Client import OK')"
python -c "from openuba.cli import main; print('CLI import OK')"
- name: Upload build artifacts
if: matrix.python-version == '3.12'
uses: actions/upload-artifact@v4
with:
name: sdk-dist
path: sdk/dist/
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: SDK CI on: push: branches: [master, dev/**] paths: - "sdk/**" pull_request: branches: [master] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: build: timeout-minutes: 30 name: Build & verify (Python ${{ matrix.python-version }}) runs-on: latchkey-small strategy: matrix: python-version: ["3.9", "3.12", "3.13"] steps: - uses: actions/checkout@v4 - name: Set up Python ${{ matrix.python-version }} uses: actions/setup-python@v5 with: cache: 'pip' python-version: ${{ matrix.python-version }} - name: Install build tools run: python -m pip install --upgrade pip build - name: Build package working-directory: sdk run: | rm -rf dist/ python -m build - name: Install from built wheel run: pip install sdk/dist/*.whl - name: Verify CLI entry point run: openuba --help - name: Verify Python imports run: | python -c "import openuba; print(f'openuba version: {openuba.__version__}')" python -c "from openuba.client import OpenUBAClient; print('Client import OK')" python -c "from openuba.cli import main; print('CLI import OK')" - name: Upload build artifacts if: matrix.python-version == '3.12' uses: actions/upload-artifact@v4 with: name: sdk-dist path: sdk/dist/
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 (3 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.