Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to 20160915 automation with_gradle
Similar to 20160915 automation with_gradle (20)
Recently uploaded
Recently uploaded (20)
20160915 automation with_gradle
- 1. Automations with Gradle FiNC Inc Yuki Nanri
- 3. Introduction • Yuki Nanri (@neonankiti) • Android Developer in FiNC.
- 4. FiNC App • Data Collection -> Analysis -> Solution -> EC • Wellness Value Chains to make people change Wellness Survey Genetic Blood Testing Survey＋ Testing Analysis Report Personalized Solutions & Contents Experts Advice SNSKnowledge Walk with taking a full swing 3 times Stretch Scapla stretch 3 times Vegetables at every meals Drink water more than 1L a day Take a Yogurt in the morning • Comprehensive Results • Body and mental status • Behavior • Risk of daily habit tasks • Recomendation etc. Fitness Task FiNC STORE Get Points • Order made・ Personal supplement • Drink • Smoothy etc. Points available in FiNC app Adapt PointsReport Tourism Healthy Contents etc. Meals Task Squat 10 timesｘ3 10 minutes walk Leave half of rice Start from vegetables at every meals
- 5. Problems Product Development Process wasn’t not Good
- 6. Especially Distribution ・manually change the pointed situations (staging, production) ・QA team used to ask us everyday distribution.
- 7. Solutions ・Buying a high spec machine. ・Ignoring QA team ・Automation
- 8. What I want to share How to build apk files quickly with flavor and build types
- 9. Gradle ・Gradle is build tool written by Groovy. ・Gradle supports Maven repository.
- 10. Gradle
- 11. How to use
- 12. Components ・Product Flavor ・Build Type ・Signing Config ・Configuration http://google.github.io/android-gradle-dsl/current/ This is require configurations
- 13. Product Flavors Product flavor is used in the situations where you want to create “freemium” or “premium” app
- 14. Build Types Each build type can choose signingConfig for release and debug
- 15. Signing Configs When you build, you need to sign with keystore file like below. (Release keystore files should be stored securely. )
- 16. Configurations Configurations are combinations of ”Flavor” and “Build Types”
- 17. Configurations
- 18. But When we try to install these different flavors, it’ll cause conflicts
- 19. Why? The same package name cannot exist at the same time
- 20. Where? But the package name is written in Android.Manifest, and looks constraints.
- 21. Beforehand The documents says ・Your device and Google Play Store look at your “Application id” ・Package in manifest is the one just for referring your R classes. http://tools.android.com/tech-docs/new-build-system/applicationid-vs-packagename
- 22. So What? Change the Application id in build.gradle
- 23. Product Flavors You can change to whatever you like.
- 24. Build Types Add prefix or suffix for debug build.
- 25. Output apks All items exist simultaneously.
- 26. Further more In some app, it still causes conflicts.
- 28. Why? Provider’s authorities must be unique.
- 29. What? Authorities in manifest also should be variable.
- 30. How? Set the key value data sets
- 31. How? Use it as variants
- 32. Summary ・Gradle has potential to replace your manual work. ・Application ID must be unique. ・Provider also must be unique.
- 33. Things I cannot tell ・I didn’t have enough time to share automation parts ・Next Part ・Automated Distribution with Fabric ・Connected JIRA tickets and Github with apis
- 34. Thank you
Editor's Notes
- 今日はちょっとFiNC Appとは違う話をするよ。
- ・QA Distribution is so much time because gradle makes us wait for a long time
- Manual Distribution takes a lot of time. So I statrted to make it easy automatically. I didn’t have enough time, so today’s one is prologue
- Commonly build like ant. We don’t have to worry about libraries dependencies and management and additions.
- Commonly build like ant. We don’t have to worry about libraries dependencies and management and additions.
- Theare are some configurations available in Android Gradle.
- Product flavor is kind of Build types. You can easily image if you want to build some versions of app. Such as freemium, premium.
- Build types are common one, It’s mostly release and debug.
- ・Buildするときはkeystoreで署名しなければならない。 ・android/debug.keystoreのデフォルトパスはandroid ・もちろん自分独自のkeystoreは作れる。 -> releaseのkeystoreは一度失うと二度とGoogle Play Storeにあげられないから、大事に保管しておこう。
- ・flavorとdebugの組みあわせ
- Build variantsから簡単に選びたい
- ・パッケージnameはAndroid.manifestに書かれている。 ・問題はなに？ ・Android manifest pacakge name isn’t changed. -> どうやって解決するか？ ・パッケージネームを変数にする。 ・違う方法を探す。 How to solve this problems 1. To change the package name from constraints to variants. 2. To find a different way.
- These should have different packages in the Google Play store such that they can be installed and purchased separately both installed at the same time. The final package that is used in your built .apk's manifest, and is the package your app is known as on your device and in the Google Play store, is the "application id". The package that is used in your source code to refer to your R class, and to resolve any relative activity/service registrations, continues to be called the "package".
- ・flavorだけでなく、リリースとデバッグでもapplication IDをわけないとインストールできないので
- ・名前も変えれる。String resouceにセットすることで。
- As
- ・認証局が必要で。その認証局はunique, ・それはcontent providerにアクセスするためのURIであればよい。
- Build gradleで変数を定義すれば、AndroidManifestでも同じように使える。
- As
- As
- As
- Manual Distribution takes a lot of time. So I statrted to make it easy automatically. I didn’t have enough time, so today’s one is prologue