Building and Testing an Automotive Platform - How Automotive Grade Linux is Built and Tested
summary
Automotive Grade Linux uses Yocto/OpenEmbedded to produce images that Jenkins (triggered from Gerrit) builds on identical OpenStack-minion images, then runs a boot-plus-test chain where results are committed per revision to a git repo. Hardware validation uses AGL JTA (containerized Jenkins jobs) for functional and benchmark suites and LAVA to manage pools of boards and remote dispatchers; boards can be Raspberry Pi, DragonBoard or vendor devboards. Post-processing and trend graphs are work in progress; goal is fast, per-commit feedback across multiple device types.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:22What is AGL
- 1:09Supported architectures
- 1:43What we do
- 2:04Our contributors
- 3:09early
- 3:55Jenkins
- 4:55Automotive Linuxorg
- 5:36Repo
- 5:57Reference Platforms
- 6:22Community Platforms
- 6:57Coffee
- 7:08Plugins
- 7:27Cloud
- 8:26Verify
- 9:46Testing on Hardware
- 11:53Documentation
- 12:10Links
- 12:38GL JTA
- 13:39Results
- 16:06The Board
- 18:17Lava
- 22:05Porter Automotive Linux
- 23:36Cost
- 24:00Postprocessing
- 25:22Key Indicators
- 27:04Garrett Jenkins
- 28:17Yocto
- 30:24oops
- 31:22Questions
related talks
43mContributing to Automotive Grade Linux and GENIVI Development Platform
49mOpen Source in Every Car with Automotive Grade Linux
35mIntroduction to AGL Architecture and Roadmap
35mAutomotive Grade Linux State of the Union
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto
33mUsing Open Source Software to Build an Industrial-grade Embedded Linux Platform...
38mBoF: Automotive Grade Linux Developer Community
48mLiving on Master: Using Yocto Project, Jenkins and LAVA for a Rolling Release