Automating and upholding quality of your Mobile App with CI/CD

Slide 1

Slide 1 text

Automating and upholding quality of your mobile app with CI/CD Peter-John Welcome @pjapplez Mobile Engineering Lead

Slide 2

Slide 2 text

About me

Slide 3

Slide 3 text

Our Road Map to Success ● Reliability ● Maintainability ● Testability ● Portability ● Reusability ● Automate Everything ● Avoid Human Error

Slide 4

Slide 4 text

Our Road Map to Success ● Branching Strategies ● Release Strategies ● Code Reviews ● Architecture ● Code Coverage ● Static Code Analysis ● CI/CD ● Automated releases

Slide 5

Slide 5 text

Branching Strategies

Slide 6

Slide 6 text

GitFlow: Source: https://tinyurl.com/y5xjsc4l

Slide 7

Slide 7 text

Trunk based: Source: https://tinyurl.com/y3xb8okn

Slide 8

Slide 8 text

Architecture

Slide 9

Slide 9 text

Architecture ● Consistency ● Code Maintainability ● Loosely coupled code ● Testability ● Design Patterns (Solving Complex Problems and reusability) ● New developer Ramp up time is faster ● Can build features faster with quality and bug free code in mind

Slide 10

Slide 10 text

Code Reviews (Pull Requests)

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

Code Reviews ● Code reviews can get messy ● Should be there to validate the business requirement ● Validate unit testing ● Good practices are being followed (Linting, Style Guides) ● A safe place to make mistakes but also learn from team members ● A place to congratulate team members on awesome work

Slide 13

Slide 13 text

Code Coverage

Slide 14

Slide 14 text

Code Coverage

Slide 15

Slide 15 text

Code Coverage

Slide 16

Slide 16 text

Static Code Analysis tools

Slide 17

Slide 17 text

Static Code Analysis: This is the analysing of software without executing it. Usually performed on source code that is not being executed. It’s basically code reviewing by an automated tool.

Slide 18

Slide 18 text

Static Code Analysis ● Linting ● Code grading ● Style guides ● Tech Debit and maintenance analysing ● Automatic code reviews

Slide 19

Slide 19 text

Static Code Analysis

Slide 20

Slide 20 text

Static Code Analysis

Slide 21

Slide 21 text

What is CI?

Slide 22

Slide 22 text

What is CI: Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.

Slide 23

Slide 23 text

CI Workﬂows:

Slide 24

Slide 24 text

What is CD?

Slide 25

Slide 25 text

What is CD? 1. Continuous delivery 2. Continuous deployment

Slide 26

Slide 26 text

What is CD (Delivery): Continuous delivery is an extension of continuous integration to make sure that you can release new changes to your customers quickly in a sustainable way. This means that on top of having automated your testing, you also have automated your release process and you can deploy your application at any point of time by clicking on a button.

Slide 27

Slide 27 text

What is CD(deployment): Continuous deployment goes one step further than continuous delivery. With this practice, every change that passes all stages of your production pipeline is released to your customers. There's no human intervention, and only a failed test will prevent a new change to be deployed to production.

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

Main reasons for CI/CD

Slide 31

Slide 31 text

Reasons for CI/CD ● Maintain a single source repository ● Automate the build ● Make your build self-testing ● Every commit should build on an integration machine ● Enforce rules on codebases ● Test in a clone of the production environment ● Make it easy for anyone to get the latest executable version ● Everyone can see what’s happening ● Automate deployment

Slide 32

Slide 32 text

Types of CI/CD Platforms ● Jenkins ● Bitrise ● SemaphoreCI ● CircleCI ● TeamCity ● Travis ● Bamboo ● Codeship

Slide 33

Slide 33 text

Automating everything (Fastlane)

Slide 34

Slide 34 text

Fastlane

Slide 35

Slide 35 text

Alternatives to Fastlane

Slide 36

Slide 36 text

Cool things we can do

Slide 37

Slide 37 text

Source: https://tinyurl.com/y5g9t49h

Slide 38

Slide 38 text

End Goal Source: https://tinyurl.com/y4wva4v9

Slide 39

Slide 39 text

Thanks! Contact me: https://medium.com/@pjwelcome @pjapplez [email protected] Peter-johnwelcome.co.za https://github.com/pjwelcome