Conquer Mobile App CI/CD Challenges Using with a Device Cloud
summary
Shows how pairing Jenkins + device cloud automates building, signing and deploying mobile binaries (APK/IPA) to real devices, not emulators, and runs tests with frameworks like Appium, XCUITest, Espresso. Calls out iOS signing and Mac build requirement, contrasts private vs public device farms, and quantifies test scale: ten iOS variants ×15 devices (≈150 runs) and broad Android permutations that push hundreds of device/OS combinations. Describes parallel execution, device utilization, and result collection back into Jenkins.
AI-written summary · about
chapters (15)
- 0:00Intro
- 3:27Gather The Source Code
- 4:06Web Architecture
- 4:47Mobile Architecture
- 5:53Build The Application - Three Types
- 11:47The Real Device Question
- 14:17The Real Device Impact on Developers CI Engineers, and Testers
- 14:57What Is a Device Cloud?
- 15:262 kinds of Device Clouds: Hosted or On-Premise
- 18:03Device Cloud Impact on Developers, CI Engineers, and Testers
- 20:47Test Automation Choice Abounds!
- 23:39Access to Real Devices in Device Cloud
- 25:50Mobile Automation Challenges
- 31:32Jenkins Example of Deploy and Test
- 34:265 Mandatory Components to Achieve Successful Mobile CUCD
related talks
41mPlug Real Devices into Your Jenkins Process and Automate Testing
20mContinuous integration for mobile
22mMobile DevOps - Streamline your iOS Builds, testing Distribution & Publish
55mJenkins CI Pipeline using Appium tests for Android and iOS
14mMobile CI at Etsy
35mDockerization of a Real Mobile Device Farm and Scalable QA Automation Ecosystem
53mCI for Android Using Jenkins
39mMobile DevOps - From Idea to App Store