Mobile DevOps 

Android Chapter Lead @ TBC Bank tatocaster.me Tato Kutalia tatocaster 

No content

Plan ● Life before DevOps ● Why DevOps matters ● CI / CD in Agile teams ● Going mobile ● Available solutions on the market 

Life before DevOps ● Business was a driver ● Monolith ● Monthly releases at most ● Each feature release had been in development and testing for multiple months already. ● QAs were struggling. Low test coverage and distribution ● Rollbacks were hard 

Life before DevOps - Tech-wise ● Sysadmins = Bottleneck ● Staging server? ● Containers? Nope ● Software vs Hardware ● Long-living branches ● Merging I believe some of you still remember pushing changes directly to prod server via FTP 

Challenges Before Development Testing Release Development Testing Release Development Testing R Release cycle Bottleneck Release #1 Release #2 Release #3 

And what if you found a bug ? 

What is DevOps 

Agile way of doing things 

DevOps .. Agile Release Testing Monitor / Support Development Start DevOps Development Operations Agile 

Rapid delivery ● Biweekly releases Parallel builds for different configurations: ● flavors (Google / Huawei) ● variants (prod/test) ● release/debug 

Feedback loop ● Fail fast ● Short-living branches ● Reduced branches ● More PRs 

Improved communication ● ✅ PRs = Happy team ● QAs + developers 

Security ● Containers ● Managing credentials ● Continuous monitoring 

Continuous Testing ● Builds for QA ● Automatic unit tests ● Automatic delivery via Firebase Beta/Slack 

Mobile DevOps? ● Adapt to mobile infrastructure ● Mobile release flow ● Mobile tools ● Keep artefacts ● Manage multi-module builds & tests ● Multiple concurrent builds 

What the market offers for mobile? ● Bitrise ● CircleCI ● Jenkins ● TeamCity ● Bitbucket Pipelines ● Travis CI ● and much more 

Questions