CI with Git Flow

Transcript

1. CI with Git Flow Prince
2. Goal • Assembling software every time code changes • Defect integration errors as quickly as possible • When we get the code from the repository, it will always build successfully and pass all tests • Auto deploy in different environments (ref)
3. Roles • RD • QA / PM / PO • Beta Users • App Store Users
4. Phases • Development • QA • Beta • Release (on App Store)
5. Deploy Environment • Development environment • dev-host • QA environment • dev-host • crashlytics • Production environment • beta-host & master-host • crashlytics / mixpanel
6. Build Type • Private build • unit test, static analysis, … • Integrated build • build DevEnv.ipa, delivery via TestFlight • Release build • build BetaEnv.ipa, delivery via TestFlight • build ProdEnv.ipa
7. Rethink Git Flow • combine Branch and Development phases
8. dev Jenkins OSX Server unit test static analysis testflight Development Phase DevEnv.ipa (BetaEnv.ipa) Private Build … every commit / manually
9. release dev Code Freeze and start QA phase QA Phase
10. release dev Tester can install ipa from TestFlight Integration Build Jenkins TestFlight DevEnv.ipa (BetaEnv.ipa) check hourly / manually QA Phase
11. release dev fix bugs on release branch Integration Build Jenkins TestFlight DevEnv.ipa (BetaEnv.ipa) check hourly / manually QA Phase
12. master release dev Beta 1 notify distribution list Jenkins TestFlight DevEnv.ipa BetaEnv.ipa Release Build manually Beta Phase ProdEnv.ipa
13. master release dev Beta 2 notify distribution list Release Build hotfix on master branch Beta Phase Jenkins TestFlight DevEnv.ipa BetaEnv.ipa manually ProdEnv.ipa
14. master release dev Tag 1.1.0 manually Release Build App Store submit Release phase ProdEnv.ipa
15. Developer CI Server TestFlight Github Data Storage Developer Developer Build ipa Run Test Deploy app Build Development Pull source CI Architecture
16. End