ci-matters

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

CI's integration

• [x] Jenkins
• [x] Travis CI
• [x] Bitrise
• [x] TeamCity
• [x] BuddyBuild
• [x] Shippable
• [x] Circle
• [x] GitHub Actions

TODO

• [ ] Nevercode.io
• [ ] Gitlab CI
• [ ] Drone.io

Comparison

Comparison table

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

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.

⚠️ This information can get outdated very quickly as services evolve. ⚠️

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)
• Nevercode.io - starts with 5$/month. (1 concurrent build, ∞ projects, 90 min. max 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)

Presentation

I gave a talk back in 2016 and this repository was a technical part for it. I am describing there configured CI's and providing my personal opinion about which CI to choose depending on your needs (in 🇷🇺 language ).

It doesn't contain information about ALL existing CI services, but should be a good start.

In few words:

• Jenkins/TeamCity for complex workflow
• Travis CI/Circle CI for open-source projects
• Bitrise.io for any workflow

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

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