1, 2, 3 build - continuous integration for mobile apps
•Télécharger en tant que PPTX, PDF•
0 j'aime•877 vues
Slides that I presented at Voxxed Days 2016 in Belgrade about Continuous Integration for Mobile Applications. I demonstrated a few online service providers and showed how you can set up a build server in just a few minutes for your mobile application and ultimately deploy it with a few clicks to the App store.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à 1, 2, 3 build - continuous integration for mobile apps
Similaire à 1, 2, 3 build - continuous integration for mobile apps (20)
Plus de Alexander Pacha
Plus de Alexander Pacha (7)
Dernier
Dernier (20)
1, 2, 3 build - continuous integration for mobile apps
- 1. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 1 1, 2, 3 - Build! Continuous Integration for mobile Apps
- 2. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 2 Motivation Setting up a Jenkins (Oh no… not again!)
- 3. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 3 “Civilization advances by extending the number of important operations we can perform without thinking” Alfred North Whitehead
- 4. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 4 Quick Survey What are you developing? • Mobile Apps • Web Apps • Desktop Apps • Other What Version Control system do you use? • Nothing • SVN • Git • Other What delivery method are you using? • Continuous Integration • Continuous Delivery • Manual Integration Which tools are you using? • Jenkins • TeamCity • Travis • Cloud-Services (Bitrise, VSTS, …)
- 5. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 5 Continuous Integration
- 6. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 6 1 Building your app
- 7. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 7 The build Repository Known compilation environment Deliverable
- 8. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 8 Known compilation environment Building for iOS, requires a Mac Depends on your project Building for Windows, requires Windows Android is supported on both platforms
- 9. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 9 Setting up your automated build - GreenhouseCI
- 10. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 10 Automatic Versioning Chose with care! Automatically version your application, that is built from the CI
- 11. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 13 Signing your app Android Keystores (self-generated) Debug vs. Release Keystore More information: • https://developer.android.com/studio/publish/app-signing.html • https://codesigning.guide/ • http://sharpmobilecode.com/making-sense-of-ios-provisioning/ iOS Identity Certificates and Provisioning Profiles Dedicated testing devices
- 12. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 14 2 Testing your mobile app
- 13. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 15 “Test early. Test often. Test automatically” Hunt and Thomas – The Pragmatic Programmer
- 14. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 16 Automated Unit-Testing Can easily be done on each platform
- 15. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 17 Automated UI-Testing • GreenhouseCI, Bitrise and Travis support Android Emulator and iOS Simulator directly • VSTS requires custom Agent: https://github.com/Microsoft/vsts-agent • On-Devices Services like • Testdroid • Xamarin Test Cloud • AWS Device Farm • Firebase • Testobject Tricky, but possible
- 16. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 18 Automated Testing
- 17. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 19 “Test your software, or your users will” Hunt and Thomas – The Pragmatic Programmer
- 18. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 20 3 Deploying your mobile app
- 19. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 21 Publishing to App Stores More info: https://github.com/Microsoft/google-play-vsts-extension Deploying to Google Play Store
- 20. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 22 Publishing to App Stores Deploying to Apple App Store
- 21. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 23 Publishing to App Stores Deploying to Apple App Store using Fastlane
- 22. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 24 Publish to (Beta-)Testers Directly publish the app to testers Available for all mobile platforms Useful features: • Insights • Crash Reports • Feedback • Auto-Updater (side-loading) HockeyApp
- 23. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 26 More tools and resources • Fabric Crashlytics, • Testflight BetaTesting for iOS More links on http://my-it.at
- 24. © Zühlke 20161, 2, 3 - Build! | Alexander Pacha 27. September 2016 Slide 27 Summary • Continuous Integration and Continuous Delivery is possible • Sometimes tricky to set it up correctly, but definitely worth the effort • Online services do cost some money, but can help you to quickly get started
Notes de l'éditeur
- Hi, Alex, Zühlke, Responsible Today talking about CI for mobile = CI for apps with special tricks Main Goals of this talk: Raise awareness, how easy it is to automate your build (including live-demonstrations) Advocate the use of cloud services over on-premise solutions Awakening desire to use this in your next project (Ultimately, you walk out of this talk and start using CIs for all your mobile projects)
- Back in Camp 2014, everyone set up a Jenkins (himself), yet no one really did it in a project. Tedious, actually quite boring, ... because it follows certain recipes that you have to do over and over again. --> OPs had the same problem. Started creating bash scripts to automate things
- Vergleich mit Autofahren Safety in Development
- Continuous Integration is the practise of merging all developer working copies into a shared mainline several times a day. Pro: Integration bugs are detected early Constant availability of “current” build for testing and release Avoid dependency on individuals for building the app If reverting is required, only small number of changes are lost Avoid last-minute chaos before release Contra: Getting up and running is not trivial Eventually costs money Someone has to take care of it
- A build is a procedure that takes an empty directory (and a known compilation environment) and builds the project from scratch, producing whatever you hope to produce as a final deliverable. Hunt and Thomas - The pragmatic programmer
- Ask audience, if this has ever happened to someone def code = System.getenv("BITRISE_BUILD_NUMBER") as Integer ?: 0 android { defaultConfig { versionCode code versionName "1.4." + code ...
- Ask audience, if this has ever happened to someone def code = System.getenv("BITRISE_BUILD_NUMBER") as Integer ?: 0 android { defaultConfig { versionCode code versionName "1.4." + code ...
- Once a person finds a bug, it should be the last time a person finds that bug. Automate a test for it
- Snapshot – Generate screenshots https://codesigning.guide/
- Be aware that you will do a lot of updating and upgrading -> Basically whenever I come back to my PC after a week, there are new updates available for Android, Xamarin, Mac, Windows, Build-Tools, Build-Agents, ... Be aware that you will do some kind of scripting (bash, PS, python, whatever)