Tags: android , gradle , android studio , apk
tl;wr: use this.
Since my last post a lot has changed, broken down and new things are possible. Let’s see what can be done now.
Previously gradle.properties contained sensitive info (passwords, duh), so it had to be .gitignore’d, that caused Could not find property errors just after repo clone and was unusable on CI systems. It can be fixed by adding:
// returns value of requested variable or default (as a fallback)
String safeGet(String name, String defaultValue = '') {
  hasProperty(name) ? project[name] : defaultValue
}
// returns file from a path provided in properties file
File safeGetFile(String name) {
    String fileName = safeGet(name, null)
    fileName != null ? file(fileName) : null
}
And replacing all project.VARIABLE occurunces with safeGet('VARIABLE'). Use safeGetFile('VARIABLE') to get files.
NOTE: Variable name is quoted in a function call.
That little trick disables instacrash™ functionality on the gradle part.
Now, let’s get local gradle.properties file back to the repo. To do that we need to move all super-secret variables somewhere safe and outside of the repo. Luckily, gradle by default also reads its global properties file: ~/.gradle/gradle.properties.
# release builds dir
# That's the default releases dir, you can override it
# for a specific project in its local gradle.properties file.
RELEASES_PARENT_DIR=/Users/mee/dev/android/binaries/
# release build signing
STORE_FILE=/Users/mee/dev/android/keys/keyname
STORE_PASSWORD=superSecretKeyPassword
# if you use one (or default) key for all apps you can include
# KEY_ALIAS and KEY_PASSWORD here. I discourage it though.
The only required variable in a local gradle.properties is KEY_ALIAS.
# Override name of the folder created in RELEASES_PARENT_DIR;
#   default is project name
FOLDER_NAME=designAdvice
# Name of the key used to sign APK in this project
KEY_ALIAS=myKeyAlias
NOTE: Remember to remove gradle.properties exclusion from .gitignore file.
If you use the same password for store and its keys you can skip to the next section, otherwise there’s one more thing to do.
Create secret.properties file in the project root:
# Key-specific password
KEY_PASSWORD=AnotherSuperSecretPass
IMPORTANT: remember to add this file to .gitignore!
Then create a function to safely attach properties to the project object:
// attach new global property to the `project`. Will not override by default
def safeLoad(String name, Object value, Boolean override = false) {
  if (!hasProperty(name) || override)
    project.set name, value
}
And finally load properties from a file:
// loads variables from a file to `project` so they can be `safeGet`-ed later
File secretPropsFile = file('../secret.properties')
if (secretPropsFile.exists()) {
  Properties p = new Properties()
  p.load(new FileInputStream(secretPropsFile))
  p.each { name, value ->
    safeLoad name as String, value
  }
}
IMPORTANT: this last snippet must be above android {} declaration.
Once that is setup, let’s take care of output APK file:
  buildTypes {
    release {
      proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
      signingConfig signingConfigs.release as Object
      minifyEnabled true
      zipAlignEnabled true
      /* construct releases dir.
        Default is `~/APKs/<projectName>`
      */
      File releasesDir = new File(
        safeGet('RELEASES_PARENT_DIR', '~/APKs'),
        safeGet('FOLDER_NAME', project.group as String)
      )
      // create path if doesn't exist
      if (!releasesDir.exists())
        releasesDir.mkdirs()
      android.applicationVariants.all { variant ->
        variant.outputs.each { output ->
          if (output.name == "release") {
            /* base file name in a form of:
              [package]-[versionType]-[versionName]-[versionCode]
              ex. com.meedamian.testApp-release-1.0.0-1111
            */
            String fileName = [
              defaultConfig.applicationId,
              project.name,
              defaultConfig.versionName,
              defaultConfig.versionCode
             ].join('-')
            // set desired path and name of the output APK file
            output.outputFile = new File(releasesDir, fileName + '.apk')
            // mapping.txt file code
          }
        }
      }
    }
  }
mappings.txt fileIf you’d also want to move mappings file replace // mapping.txt file code with:
// copy mappings.txt
if (variant.getBuildType().isMinifyEnabled()) {
  File mappingDir = new File(releasesDir, 'mappings')
  if (!mappingDir.exists())
    mappingDir.mkdirs()
  assemble << {
    copy {
      from variant.mappingFile
      into mappingDir
      rename 'mapping.txt', "mapping-${fileName}.txt"
    }
  }
}
versionCodeI know it’s nasty, and I would love to see suggestions on how this can be done better :).
build.gradle:Integer getBuildVersion(defaultVersion, Boolean increment = false) {
  File verFile = file('../version.properties')
  if (!verFile.canRead())
    verFile.createNewFile()
  Properties props = new Properties()
  props.load new FileInputStream(verFile)
  String currentCodeVersion = props['VERSION_CODE']
  if (currentCodeVersion == null)
    currentCodeVersion = defaultVersion ?: android.defaultConfig.versionCode
  if (increment) {
    Integer bumpedCodeVersion = currentCodeVersion.toInteger() + 1
    android.defaultConfig.versionCode = bumpedCodeVersion
    props['VERSION_CODE'] = bumpedCodeVersion.toString()
    props.store verFile.newWriter(), "Build version updated with each release build"
    currentCodeVersion = bumpedCodeVersion
  }
  currentCodeVersion as Integer
}
versionCode references with calls to getBuildVersion():First one is defaultConfig definition:
defaultConfig {
  applicationId "com.yourPackage.someMore"
  minSdkVersion 15 // because #minSDK15
  targetSdkVersion 22
  versionCode getBuildVersion(1)
  versionName "0.0.1"
}
Second one is fileName construction:
String fileName = [
  defaultConfig.applicationId,
  project.name,
  defaultConfig.versionName,
  getBuildVersion(android.defaultConfig.versionCode, true)
].join('-')
It appears that it’s a wider topic and I’ll address it in a next post. (But if you don’t feel like waiting - use this awesome plugin).
Since originally published this article was edited:
And that’s it. Here’s a complete version again.