Backend CI workflow (GACWR/OpenUBA)
The Backend CI workflow from GACWR/OpenUBA, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get run de-duplication, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Backend 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: Backend CI
on:
push:
branches: [master, dev/**]
paths:
- "core/**"
- "requirements.txt"
- "docker/backend.dockerfile"
pull_request:
branches: [master]
jobs:
lint:
name: Lint & type check
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: "3.12"
cache: pip
- name: Install dependencies
run: |
pip install --upgrade pip
pip install -r requirements.txt
- name: Run mypy type check
run: |
mypy core/ --ignore-missing-imports --explicit-package-bases || true
test:
name: Unit tests (Python ${{ matrix.python-version }})
runs-on: ubuntu-latest
strategy:
matrix:
python-version: ["3.9", "3.12"]
steps:
- uses: actions/checkout@v4
- name: Set up Python ${{ matrix.python-version }}
uses: actions/setup-python@v5
with:
python-version: ${{ matrix.python-version }}
cache: pip
- name: Install dependencies
run: |
pip install --upgrade pip
pip install -r requirements.txt
- name: Run unit tests
run: |
pytest core/tests/ -v --tb=short -k "not e2e and not integration" \
--junitxml=test-results.xml || true
- name: Upload test results
if: always()
uses: actions/upload-artifact@v4
with:
name: test-results-py${{ matrix.python-version }}
path: test-results.xml
import-check:
name: Verify imports
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: "3.12"
cache: pip
- name: Install dependencies
run: |
pip install --upgrade pip
pip install -r requirements.txt
- name: Verify core module imports
run: |
python -c "from core.fastapi_app import app; print('FastAPI app imports OK')"
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Backend CI on: push: branches: [master, dev/**] paths: - "core/**" - "requirements.txt" - "docker/backend.dockerfile" pull_request: branches: [master] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: lint: timeout-minutes: 30 name: Lint & type check runs-on: latchkey-small steps: - uses: actions/checkout@v4 - name: Set up Python uses: actions/setup-python@v5 with: python-version: "3.12" cache: pip - name: Install dependencies run: | pip install --upgrade pip pip install -r requirements.txt - name: Run mypy type check run: | mypy core/ --ignore-missing-imports --explicit-package-bases || true test: timeout-minutes: 30 name: Unit tests (Python ${{ matrix.python-version }}) runs-on: latchkey-small strategy: matrix: python-version: ["3.9", "3.12"] steps: - uses: actions/checkout@v4 - name: Set up Python ${{ matrix.python-version }} uses: actions/setup-python@v5 with: python-version: ${{ matrix.python-version }} cache: pip - name: Install dependencies run: | pip install --upgrade pip pip install -r requirements.txt - name: Run unit tests run: | pytest core/tests/ -v --tb=short -k "not e2e and not integration" \ --junitxml=test-results.xml || true - name: Upload test results if: always() uses: actions/upload-artifact@v4 with: name: test-results-py${{ matrix.python-version }} path: test-results.xml import-check: timeout-minutes: 30 name: Verify imports runs-on: latchkey-small steps: - uses: actions/checkout@v4 - name: Set up Python uses: actions/setup-python@v5 with: python-version: "3.12" cache: pip - name: Install dependencies run: | pip install --upgrade pip pip install -r requirements.txt - name: Verify core module imports run: | python -c "from core.fastapi_app import app; print('FastAPI app imports OK')"
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.
- 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
- End-to-end and browser tests
This workflow runs 3 jobs (4 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.