Continuously integrating at ease! / a GitLab CI story

Continuous Integration (CI) is the process of automating the build and testing of code every time a team member commits changes to version control. In this talk I'll talk about what should we expect from a modern CI solution and what is our approach at InterTicket. What should happen for every line of code that is checked into a repository? What are these strange words: pipelines, stages and jobs everyone talks about?

Transcript

1. Continuously integrating at ease! a GitLab CI story interticket
2. agenda • introduction • continuous integration • development flow • branching strategy • CI solutions • setup • pipelines and stuff • summary • questions interticket
3. introduction interticket
4. introduction • Hi, I'm Richard • iOS developer since 2014 • leading the mobile efforts @interticket interticket
5. introduction • interticket is • a ticket company - jegy.hu • selling tickets in 15+ country • we have other interesting projects as well • 10 man strong mobile team interticket
6. continuous integration interticket
7. –Martin Fowler “Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.” interticket continuous integration / what?
8. interticket continuous integration / why? • easier integration • every change is verified by your standards • the result is more cohesive software
9. interticket continuous integration / how? hopefully the rest of the presentation will answer this question
10. development flow interticket
11. interticket development flow
12. branching strategy interticket
13. interticket branching strategy / simplified • master • development • topic branches
14. CI solutions interticket
15. interticket CI solutions / why not Jenkins? • plugin ecosystem is a pain to manage • hard to setup • UX disaster • pipelines are new
16. interticket CI solutions / our requirements • versioned • supports gitlab • scalable • easy configuration • docker compatibility • lightweight
17. interticket CI solutions / why GitLab CI? • all our requirements were checked • source control & CI in the same place • we love OSS • GitLab is a really nice software, we expect the same from their CI solution
18. setup interticket
19. interticket setup / .gitlab-ci.yml • this is the file where you configure what CI does with your project • place it in the root of you repository • GitLab will look for this at pushes to your repository
20. interticket setup / .gitlab-ci.yml example stages: - build - test test: stage: test script: - xcodebuild -scheme "$DEBUG_SCHEME" -destination "$SIMULATOR_DEVICE" test only: - branches
21. interticket setup / gitlab-runner • runners are the heart of GitLab CI • open source tool to manage runners • Settings -> CI / CD
22. pipelines and stuff interticket
23. interticket pipelines and stuff • pipelines • stages • jobs • scheduled pipelines • how do we use it @interticket?
24. interticket pipelines and stuff / pipelines • runs for each pushed change • 1 push = 1 pipeline • 1 pipeline = stages x jobs
25. interticket pipelines and stuff / pipelines
26. interticket pipelines and stuff / stages • 1 pipeline can have n number of stages • grouping for your jobs • jobs inside executed in parallel
27. interticket pipelines and stuff / stages stages: - build - test - deploy
28. interticket pipelines and stuff / jobs • status • failed • pending • running • cancelled • success • etc • defined in .gitlab-ci.yml
29. interticket pipelines and stuff / jobs danger: stage: build script: - bundle exec danger --fail-on-errors=true merge-request: stage: build script: - bundle exec fastlane merge_request unit-test: stage: test script: - bundle exec fastlane unit_test except: - schedules test: stage: test script: - bundle exec fastlane test only: - schedules crashlytics-beta: stage: deploy script: - bundle exec fastlane beta only: - development except: - schedules
30. interticket pipelines and stuff / scheduled pipelines • you can schedule a pipeline via a cron like environment in GitLab
31. interticket pipelines and stuff / scheduled pipelines
32. interticket pipelines and stuff / other stuff • job artifacts • support submodules • triggering pipelines • secret variables
33. interticket pipelines and stuff / how do we use it @interticket? on each push to the repository danger static analysis unit tests generate reports on code quality on each merged merge request release to fabric everyday @4AM run UI tests
34. interticket summary • good for your sanity as it reduces risk and makes it easier to deploy code • makes your team happier • generate analysis & reporting • doesn't matter which one you use, but pick one!
35. interticket Questions?
36. interticket Thanks! Richard Szabo Mobile Lead @interticket richard.szabo@interticket.net
37. sources • https://speakerdeck.com/adhumi/test-and-distribute-an-ios-app-with-gitlab-ci • https://docs.gitlab.com/ee/ci/README.html • https://www.martinfowler.com/articles/continuousIntegration.html • https://speakerdeck.com/adhumi/test-and-distribute-an-ios-app-with-gitlab-ci • https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows interticket