Download to read offline
Uploaded byEvan Schultz
Fixing Continuous Delivery For Mobile
This document discusses continuous delivery for mobile applications. It defines continuous integration, continuous delivery, and continuous deployment. It describes using tools like CircleCI for continuous integration to keep codebases clean and deployable. Continuous delivery means actually deploying deployable code, which can be challenging for mobile apps. The document then discusses how continuous deployment aligns with Agile principles and can save money. It addresses issues that can arise like long pull requests and solutions like pairing programming and automating tests. Hot pushing code changes to devices is important but existing solutions were limited so the author created Cordwood and later replaced it with using CodePush with CircleCI for per-pull request pushes.
More Related Content
Similar to Fixing Continuous Delivery For Mobile
Fixing Continuous Delivery For Mobile
- 1. 2016 Rangle.io 129 Spadina Ave.,Suite 600 Toronto, ON M5V 2L3 Canada evan@rangle.io Fixing Continuous Delivery for Mobile Evan Schultz Javascript Architect rangle.io @e_p82 @rangleio Twitter:
- 2. Continuous Integration Continuous Delivery ContinuousDeployment what is continuous delivery?
- 3. “Build” multiple daystimes per day / after every merge. Add unit tests, linting, beautification, etc. Linked together with a tools such as Gulp. Many solutions. We like CircleCI. Why? To keep master “clean” and “working”. continuous integration
- 4. Producing something ofvalue* at frequent intervals. Keeping master deployable. continuous delivery
- 5. Actually deploying “deployable”code. Can be tricky on the backend, easy for the front end… excluding mobile apps. continuous deployment
- 6.
- 7. continuous deployment =better Agile CD Agile
- 8. Build what isactually needed. discuss working software focus on what's next ruthlessly prioritize Avoid work in progress. Save Money Realize ROI and learning earlier Deliver 80% of the value with 20% of the effort. Like Agile, it helps…
- 9. Deliver Early forValue and/or Learning Image by xoque Lean towards learning (lean startup) Lean towards tangible value (classic scrum)
- 10. Good user stories/featureslicing Limit WIP Reduce cycle time How to Achieve CD In General?
- 11. Buggy Software =Work in Process
- 12. Deferred Bug FixingCosts More
- 13. Ergo, leaving testingto testers is often problematic. Effectively, you end up with a mini-waterfall inside the iteration. We aim for truly continuous delivery, where every merge is deployable. So, how do you approach testing? Short answer: testing is everyone’s job. This raises the urgency of deploying your software. Again… Deferred Bug Fixing Costs More
- 14.
- 15. Cycle time WIP If theseare high, debug the process. How to Measure if CD is Working
- 16.
- 17.
- 18. Life of APull Request Testing is one of the biggest lags Design too, often due to regressions found during development. Access to running code on device is essential. Cost of fixing bugs? The impact of PRs stacking is massive. UX Design Dev Design Test
- 19.
- 20. Designer works withthe team Pair designing as well as pair programming when friction occurs Relentlessly measure WIP and Cycle Time and fix issues expect team to need time to ramp up automate everything understand the value (tacit knowledge) Solutions in the Team
- 21. PRs need tobe closed in < x hrs What is x? It depends on when you feel friction or pain WIP goes up? It usually means PRs not being closed This results in more development against slightly different codebases This means more regressions So… Solutions in the CD Pipeline
- 22.
- 23. Builds take time Deploystake time Testers can't be immediately available Massive impact on flow, leading to… Bigger PRs Longer PRs More regressions, more testing But…
- 24. CodePush Circle CI Heroku-style PRdeploys deploy different PRs as needed which enables to… Our Solution
- 25. Hot push acrossdev lifecycle
- 26. phonegap-plugin-contentsync Ionic push nordnet cordova-hot-code-push MicrosoftCode Push Rangle Cordwood It’s too much! But we wanted hot push across dev lifecycle. But…lots of Recent Hot Push Solutions
- 27.
- 28. CircleCI hooks Per-PR hotpush client-side UI to pick PRs deploy once, and presto! On demand device config for testing across the dev. lifecycle but Cordwood is dead (more later) Cordwood has…
- 33.
- 34. Many options aroseat same time so it didn’t make sense to continue Our goal: a solution that worked across all our JavaScript mobile projects Lots of Recent Hot Push Solutions
- 35.
- 36. https://microsoft.github.io/code-push/ Handles the pushwell No solution for per-PR pushes Circle-CI, some node scripts, and some API digging solved this. https://github.com/rangle/code-push-demo CodePush
- 38. Now in slowmotion…
- 43.
- 44.
- 45. Thank You Evan Schultz evan@rangle.io @e_p82 @rangleio 129Spadina Ave., Suite 600 Toronto, ON M5V 2L3 Canada