Building CI pipeline based on TeamCity & Docker in Android Team
summary
Describes how an Android team used TeamCity plus Docker to build a self-hosted CI pipeline as an alternative to hosted CI services. Focuses on addressing long build times and limited resources—particularly when running instrumented tests on Android Emulator—by simplifying TeamCity setup with Docker and applying optimizations to reduce management overhead so no dedicated DevOps hire is required.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:58THE NEED OF CONTINUOUS INTEGRATION
- 4:10PREDEFINED SET OF CONFIGURATIONS
- 4:53VM WITH LIMITED RESOURCES - FROM ANDROID DEV PERSPECTIVE
- 9:23HOW TEAMCITY WORKS? - SERVER-SIDE CHECKOUT MODE
- 13:14TEAMCITY - CUSTOM SETUP WITH DOCKER FOR ANDROID DEV
- 14:42TEAMCITY - PROJECT SETUP
- 15:34TEAMCITY - BUILD STEPS CONFIGURATION
- 16:08TEAMCITY - IDE PLUGIN
- 18:07TEAMCITY - MAINTENANCE WITHOUT DEVOPS
- 18:59TEAMCITY - PROJECT STATISTICS
- 20:47EL TEAMCITY - ANDROID CLIENT APP
- 23:27TEAMCITY - BUILD STEPS IN KOTLIN OSL
related talks
37mAndroid meets Docker
25mMobile DevOps - How CI/CD can change your development world
34mFrom build to Continuous Delivery in TeamCity
34mPractical tips for succeeding with CI/CD for Android
24mLessons in CI_CD from 3500 Android Teams
38mA recipe for a CI/CD pipeline
54mUsing Docker in CI
31mBuilding a private CI/CD pipeline with Java and Docker in the Cloud