Save precious time with GitHub Actions
summary
Arduino automates both software and hardware CI using Arduino CLI and self-hosted Raspberry Pi runners that flash boards, exercise I/O via pogo-pin fixtures and an FPGA monitor, and push pass/fail reports back into GitHub Actions. Over 250 public repos and ~100k users of the CLI drive tests across Linux, macOS, Windows, x86 and ARM. The team runs hardware-in-the-loop in-factory racks, generates docs and releases the CLI about every two weeks, and the pipeline is production-stable.
AI-written summary · about
chapters (14)
- 0:00Introduction to GitHub Actions
- 1:05Arduino's open-source ecosystem
- 3:17Challenges with legacy CI/CD tools
- 5:05GitHub Actions revolution
- 6:29Testing physical hardware
- 8:18Arduino CLI testing setup
- 9:25Self-hosted runners for hardware
- 11:13Automating releases with Actions
- 12:17Error detection and filtering
- 13:03Documentation generation
- 14:28Community-driven Actions
- 15:34Advanced GitHub Actions use cases
- 17:00Encouragement to try Actions
- 19:50Q&A session
related talks
01h 00mIntroduction to GitHub Actions
59mIntroduction to GitHub Actions
30mSpend More Time Coding & Automate the Boring Stuff
01h 28mAutomating Developer Things with GitHub Action
21mAzure Pipelines and GitHub Actions
48mCICD with Github Actions
42mThere’s an Action for That! Exploring the Possibilities of GitHub Actions
18mAutomating All the Code & Testing Things with GitHub Actions