title: Android Studio vs command line compile /w gradlew
body: <p>As described <a href="https://developer.android.com/studio/build/building-cmdline.html" rel="nofollow noreferrer">here in the Android Studio docs</a>, one can build an Android app from the command line with the gradle wrapper generated by Android Studio. The command line window in Android Studio shows exactly this, i.e. a call to gradlew assembleDebug (or a similar task). However starting a terminal on macOS and calling the gradle wrapper with that exact call sometimes yields other results, i.e. either <a href="https://stackoverflow.com/questions/45762245/android-studio-build-works-gradle-command-line-fails">one is able to build from Android Studio</a>, <a href="https://stackoverflow.com/questions/18837922/build-fails-inside-android-studio-command-line-works">or the command line</a>, or both (which is ideal, but unfortunately not always true).</p>
  
  <p>Who can explain what other settings the Android Studio IDE sets for their environment and where to find them, how to reproduce these settings easily in a CI environment (e.g. Jenkins, Bamboo, ...) and how one would consistently store these settings in a VCS along an Android project.</p>