How to build and test your snaps automatically using GitHub actions
summary
Automates building and testing of about 70 snaps using GitHub Actions to run two workflows: a nightly sync that updates hardcoded versions and architectures, and a PR workflow that builds a candidate snap. Builds use Launchpad remote build for multiple architectures including RISC‑V, creates an automated call‑for‑testing GitHub issue with screenshots, and requires scoped secrets (separate candidate and stable creds). Example: Signal Desktop updates reach users within ~24 hours, showing the system works end‑to‑end.
AI-written summary · about
chapters (8)
- 0:00Automated snap building intro
- 1:50Snap requirements
- 3:18CI/CD workflow overview
- 8:38Updating snap versions
- 12:21Workflow demo and testing
- 15:59Secure credentials
- 18:51Resources and next steps
- 21:41Q&A
related talks
54mDelivering code with GitHub Actions
01h 47mDeveloper Workflow Automation with GitHub Actions
21mAzure Pipelines and GitHub Actions
45mLights, Camera, GitHub Actions!
18mDeveloper Workflow Automation with GitHub Actions (CI/CD)
48mBuilding an Android CI Pipeline With GitHub Actions
44mCI/CD with GitHub Actions
01h 00mIntroduction to GitHub Actions