How we implement CI/CD on Android

1. BEKRAF - INDONESIAN AGENCY FOR CREATIVE ECONOMY
Continuous Integration and Continuous Delivery
Rendra Toro
OLX Indonesia
Intel Innovator

2. CHALLENGE - BUGS AND APPLICATION CRASHES
3

3. RESULT - BAD USER REVIEWS
4

4. CHALLENGE - LONG FEATURE RELEASES
5
IDEA
FEATURE

5. CONTINUOUS DELIVERY
6
Reducing
Risk
& Waste
Rapid Release
Customer Feedback
Innovate

6. TEST DRIVEN DEVELOPMENT
7

7. FUNCTIONAL TESTING
8

8. CONTINUOUS INTEGRATION
9

9. DEPLOYMENT
10

10. BETA VERSION DISTRIBUTION
11
Crash Reports
Feedback from testers
Analytics

11. CONTINUOUS DELIVERY
12
1. PLAN
2. CODE
4.
TEST
3.
BUILD
8.
RELEASE
5. DEPLOY
7. MONITOR
6.
OPERATE

17. What we have Learn
• Define your git flow, don’t
mess up with your master
branch (keep clean), create
another branch and create
Pull Request to order
Jenkins to build test and
merge to master if
successful. (In term of
Github, closer/faster and
stable would be better).
• Merge your test repository
along with your platform
repository.
• Write unit test by default,
the developer is responsible
to write unit testing for any
feature that he/she wrote.
• We are still using docker or
create environment based
on docker, we cant run it on
Jenkins-Slave that was
docker (Don’t do Docker in
Docker for CI).

18. Branching

19. Branching

21. 21
Master github Unit Test Build APK FTP to Server Functional Test
Dev Push
run Webhook
Artifactory
Server 1 for
Emulator
Server 2 for
Emulator
Server 3 for
Emulator
Server 4 for
Emulator

22. Appium Hub
Report Builder Artifact APK
Test
Emulator Emulator Emulator Emulator
Server 1 Server 2 Server 3 Server 4

23. BEKRAF - INDONESIAN AGENCY FOR CREATIVE ECONOMY
ThankYou