Build and Test workflow (hbldh/bleak)
The Build and Test workflow from hbldh/bleak, explained and optimized by Latchkey.
CI health: A - excellent
Point runs-on at Latchkey and get job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Build and Test workflow from the hbldh/bleak 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: Build and Test
on: workflow_dispatch
jobs:
build_android:
name: "Build Android"
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v4
- name: Install dependencies
run: pip install buildozer cython
- name: Cache buildozer files
uses: actions/cache@v4
id: buildozer-cache
with:
path: |
~/.buildozer
examples/kivy/.buildozer
key: build-cache-buildozer
- name: Clean bleak recipe for cache
if: steps.buildozer-cache.outputs.cache-hit == 'true'
working-directory: examples/kivy
run: buildozer android p4a -- clean-recipe-build --local-recipes $(pwd)/../../bleak/backends/p4android/recipes bleak
- name: Build Kivy example
working-directory: examples/kivy
run: buildozer android debug
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Build and Test on: workflow_dispatch jobs: build_android: timeout-minutes: 30 name: "Build Android" runs-on: latchkey-small steps: - uses: actions/checkout@v4 - name: Install dependencies run: pip install buildozer cython - name: Cache buildozer files uses: actions/cache@v4 id: buildozer-cache with: path: | ~/.buildozer examples/kivy/.buildozer key: build-cache-buildozer - name: Clean bleak recipe for cache if: steps.buildozer-cache.outputs.cache-hit == 'true' working-directory: examples/kivy run: buildozer android p4a -- clean-recipe-build --local-recipes $(pwd)/../../bleak/backends/p4android/recipes bleak - name: Build Kivy example working-directory: examples/kivy run: buildozer android debug
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. - 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.