The Cross-Platform Build Pipeline • Check in code • Run a build (compile) • Run tests - Mocha, or Jasmine and Protractor after build • Run Cordova build • Create binary deployable files -> APK, IPA, XAP file (platform binaries) • Deploy platform binary to a emulator • Run functional tests on the emulator -> Espresso from Google, mock wire • Signing or packaging • Submit to test store (internal, beta testing) • Send emails to beta testers with links to the app

1. Continuous Delivery for Cross-
Platform Mobile Apps
Mobile
DC

2. Presented By

5. Agenda
● Terminology
● Sample mobile project
● Continuous Delivery Pipeline
● Demo
● Discussion

6. Terminology

7. The Agile Workflow

8. Continuous Integration

9. Continuous Delivery

10. Delivery vs. Deployment

11. DevOps

12. The CD Pipeline

13. A Good CD Pipeline
● Designed to support business operations
● Build automation
● Test automation and coverage
● Notifications
● Provisioning

14. CD Value Proposition
● Paradigm shift for businesses used to yearlong release
cycles
● Ability to push code to production very rapidly
● Manual labor - minimum overhead, maximum oversight
● Early integration saves time
● Fewer issues in production
● Higher developer productivity

15. CD Tools
● Go CD - pipeline is a first class citizen, built with
CD in mind. Smaller community and plugin base
● SnapCI - Same as Go, but a hosted solution
(keep eye on this, its future might be bright)
● Jenkins - simple to setup and use

16. ● Native
○ iOS - XCode - Objective C or Swift
○ Android - Android Studio - Java
○ Windows Phone - .NET Studio - C#
● Hybrid
○ JavaScript
○ AngularJS
■ Ionic Framework
■ AppGyver Steroids
● Nybrid
○ Xamarin
○ ReactJS Native
○ AppGyver Supersonic
Mobile Platforms

17. Today
● Cross-Platform Mobile App
● Built on Ionic Framework, AngularJS and Cordova
● Built for Android
● Google Play Store APIs
● Jenkins CD Pipeline

23. Demo