In this chapter, we will see how we can organize a workflow in which we automate the process of testing and delivering your app. You can do this for both the ad hoc and the public releases of your app. To make the build-measure-feedback loop really work for you, you need to release early and often.
You can install Jenkins or TeamCity on a build server or another dedicated machine to make a new build of your app each time a new feature becomes available. Basically it comes down to that, but there are many interesting strategies to consider. For example, what is your branching strategy (Git workflow)? Do you want to run unit or UI-tests on the build server? How can you support variants (Android) or targets (iOS) for your app? Let's find out in this chapter.
We will have a look at various tools that can help us with the ad hoc distribution of the app. Some...