# Continuous Delivery for Android

DevFeed: [Continuous Delivery for Android](<https://devfeed.tech/articles/continuous-delivery-for-android-30587.md>)

Original publisher: [Read original article](<https://ryanharter.com/blog/2018/05/continuous-delivery-for-android/>)

Published: 2018-05-24T20:15:03Z

Content type: tutorial

Language: en

Sources: [Blogs on Ryan Harter](<https://devfeed.tech/sources/blogs-on-ryan-harter.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [CircleCI](<https://devfeed.tech/topics/circleci.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [Jenkins](<https://devfeed.tech/topics/jenkins.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [circleci](<https://devfeed.tech/tags/circleci.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>), [releases](<https://devfeed.tech/tags/releases.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## AI overview

An Android developer describes moving from continuous integration to continuous delivery, where app changes are automatically built and released to appropriate channels. The article discusses release targets, separate debug and release builds, and a CircleCI 2.0 workflow, with Jenkins mentioned as a previous option.

## Source excerpt

For a long time I've been in search of a good continuous integration server for Android. I've even written about one that I used years ago, which is no longer suited to Android development, in my opinion. As the Android community has grown, so has the wealth of tools available. In that time I've also moved from simply wanting continuous integration, to wanting continuous delivery. Continuous Delivery you say? Continuous delivery builds on continuous integration, but instead of just testing your source code when you commit, it is also published to the appropriate channels. This takes the burden from the developer by automatically releasing a new version of the app any time changes are made, and also creates a reliable, repeatable release pipeline.