A Brief History of Skyfarm
summary
History of Skyfarm: PlayStation builds an internal farm to manage proprietary devkits, starting with vinyl checkout tokens, then a checkout script, then a hackathon project named Skynet that wins and becomes productized into a service used in California, Tokyo and India. System handles multi-gigabyte firmware pushes, enforces low risk and tight notifications, runs under a few hundred to <1000 devices, uses Appium for tests and Python backend, hits scalability and statefulness pain, moves to stateless agents, local firmware caching and configurable health definitions.
AI-written summary · about
chapters (22)
- 0:00Skyfarm and dev kits
- 1:04Managing kits with vinyl records
- 2:08Automation with developer script
- 3:15Skynet hackathon win
- 3:58Productizing script into service
- 6:09Lessons learned and hard questions
- 7:14Overengineering and when automation is unnecessary
- 7:55Configuration latency challenges
- 9:19Settings discovery and language barriers
- 10:22Risk tolerance and kit damage
- 11:26Notifications for out of bounds devices
- 12:28Configuration complexity
- 13:57Defining device health
- 14:38Privacy and access control
- 15:42Encouraging device contributions
- 16:47Release management and timeouts
- 18:12Adding new devices
- 18:54Scaling challenges
- 20:23Future of device management
- 21:46Generic resources and platform independence
- 22:30Configurable health definitions
- 22:53Q&A
related talks
36mFarming Together
14mMobile Farming for Perfection
35mBoost your testing with Testing Farm
39mOverview of Device Farms for Mobile Testing
41mThe Android Device Farm That Fits in a (Cloudy) Pocket
29mPros and Cons of Device Farms Available for Android
48mBoard Farm APIs for Automated Testing of Embedded Linux - An Update
25mPlatform-First Mobile Automation