ci-matters

Integration (comparison) of different continuous integration services on Android project

ci-matters

Integration (comparison) of different continuous integration services on Android project.

CI’s integration

TODO

  • [ ] GreenHouse
  • [ ] Gitlab CI
  • [ ] Circle CI
  • [ ] Drone.io

Comparison

Comparison table

This table should help people make a decision which CI to choose for the project.

| CI | :dancers:,:construction_worker:,:mag_right::bug:,:vertical_traffic_light:,:mailbox_with_mail: | :iphone::eyes: | :rocket: | :page_facing_up: | :chart_with_upwards_trend: | :bust_in_silhouette::raised_hands:/:cloud: | :radio:/:computer: | :dollar: | | ————- |:—:|:—:|:—:|:—:|:—:|:—:|:—:|:—:|:—:|:—:|:—:|:—:| | Jenkins |:star:|:star:|:star:|:star:|:star:|:bust_in_silhouette::raised_hands:|:radio:/:computer:|:free:| | TeamCity |:star:|:star:|:star:|:star:|:star:|:bust_in_silhouette::raised_hands:/:cloud:|:computer:|:moneybag::moneybag::moneybag:| | Travis CI |:star:|:star:|:star:|:star:|:x:|:cloud:|:computer:|:moneybag::moneybag:| | Bitrise |:star:|:star:|:star:|:star:|:x:|:cloud:|:computer:|:moneybag::moneybag:| | Shippable |:star:|:star:|:star:|:star:|:x:|:cloud:|:radio:|:moneybag:| | Buddybuild |:star:|:star:|:x:|:x:|:x:|:cloud:|:computer:|:moneybag::moneybag:| | Gitlab CI |.|.|.|.|.|.|.|:moneybag:| | Circle CI |.|.|.|.|.|.|.|:moneybag:| | GreenHouse |.|.|.|.|.|.|.|:moneybag::moneybag:| | Drone.io |.|.|.|.|.|.|.|:moneybag:|

  1. :dancers: - clone 2. :construction_worker: - build 3. :mag_right::bug: - test 4. :vertical_traffic_light: - analyse 5. :mailbox_with_mail: - notify
  2. :iphone::eyes: - UI tests 7. :rocket: - deploy 8. :page_facing_up: - configuration file 9. :chart_with_upwards_trend: - visual reports
  3. :bust_in_silhouette::raised_hands:/:cloud: - self-hosted/cloud 11. :radio:/:computer: - CI user interface (old/new) 12. :dollar: - price

Pricing

All listed CI’s provide free plan with some restrictions like “open-source projects only” or “only 1 build node”, but it’s enough to configure the build process and check if CI suits or not.

Free plans

Choosing a free plan for a project is more suitable for a freelance project. Usually, some services provide limits on such plans for understandable reasons.

Paid plans

CI’s have different approaches and different paid plans. Check every CI pricing information for more details and choose the best option for you.

What might matter is the starting price for paid plan:

  • Jenkins - starts with X$. (paid version (Cloudbees), no public information)
  • Travis CI - starts with 69$/month. (1 concurrent build, ∞ projects, ∞ build time)
  • Bitrise - starts with 50$/month. (1 concurrent build, ∞ projects, 45 min. max build time)
  • TeamCity - starts with 299$. (4 concurrent builds, 30 project configurations, ∞ build time)
  • Shippable - starts with 25$/month. (2 concurrent builds, ∞ projects, ∞ build time)
  • Gitlab CI - starts with 15$/month. (2 concurrent builds, ∞ projects, ∞ build time)
  • Circle CI - starts with 39$/month. (2 concurrent builds, ∞ projects, 500 minutes build time per month)
  • GreenHouse - starts with 49$/month. (1 concurrent build, ∞ projects, ∞ build time)
  • Drone.io - starts with 25$/month. (1 concurrent build, 5 private projects, ∞ build time)
  • Buddybuild - starts with 79$/month. (1 concurrent build, ∞ projects, ∞ build time)

Checkstyle

Project uses custom Checkstyle rules.


Fabric/Crashlytics project configuration

In order to upload APK to Crashlytics project should have following configuration: ${projectDir}/fabric.properties file with apiSecret and io.fabric.ApiKey in AndroidManifest.xml(1, 2) file. Both keys should not be uploaded to the repository for security reasons!

Pass both parameters to your build from command line:

./gradlew -PfabricApiKey="YOUR_API_KEY" -PfabricApiSecret="YOUR_API_SECRET" crashlyticsUploadDistributionDebug

or export these keys as environment variables on a build machine and they will be automatically read from there during the build (no need to pass keys as parameters in this case).


Coveralls

Coverage Status

Coveralls provides test coverage information. COVERALLS_REPO_TOKEN environment variable should be exported on the build machine.

Related Repositories

ci-matters

ci-matters

Integration (comparison) of different continuous integration services on Android project ...