scheduler workflow (kkdai/youtube)
The scheduler workflow from kkdai/youtube, explained and optimized by Latchkey.
CI health: A - excellent
Run this on Latchkey for self-healing, caching, and up to 58% lower cost.
Grade your own workflow free or run it on Latchkey →What it does
This is the scheduler workflow from the kkdai/youtube 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: scheduler
on:
schedule:
- cron: '0 0 */1 * *'
jobs:
test:
strategy:
matrix:
platform: [ubuntu-24.04]
go-version: [1.26.x]
runs-on: ${{ matrix.platform }}
name: integration tests
env:
GOBIN: /tmp/.bin
steps:
- name: Check out code into the Go module directory.
uses: actions/checkout@v3
- name: Install Go.
uses: actions/setup-go@v4
with:
go-version: ${{ matrix.go-version }}
- name: Install ffmpeg
run: |
sudo apt-get update
sudo apt-get install ffmpeg
- name: Run tests
run: make test-integration
- name: Archive artifacts
uses: actions/upload-artifact@v4
with:
name: output
path: output
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: scheduler on: schedule: - cron: '0 0 */1 * *' jobs: test: timeout-minutes: 30 strategy: matrix: platform: [ubuntu-24.04] go-version: [1.26.x] runs-on: ${{ matrix.platform }} name: integration tests env: GOBIN: /tmp/.bin steps: - name: Check out code into the Go module directory. uses: actions/checkout@v3 - name: Install Go. uses: actions/setup-go@v4 with: go-version: ${{ matrix.go-version }} - name: Install ffmpeg run: | sudo apt-get update sudo apt-get install ffmpeg - name: Run tests run: make test-integration - name: Archive artifacts uses: actions/upload-artifact@v4 with: name: output path: output
What changed
- 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.