External properties support for your gradle builds.
Using the old com.novoda:build-properties-plugin
? You should migrate away
from it as soon as possible.
Gradle builds are highly configurable through various properties. Rather than hardcoding these properties in your build scripts, for security reasons and in order to increase modularity, it's a common practice to provide these properties from external sources.
This plugin aims to provide a simple way to:
Apply the plugin from jCenter as a classpath dependency:
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.novoda:gradle-build-properties-plugin:0.4.1'
}
}
apply plugin: 'com.novoda.build-properties'
or from the Gradle Plugins Repository:
plugins {
id 'com.novoda.build-properties' version '0.4.1'
}
Add a buildProperties
configuration to your build script listing
all the properties files you intend to reference later on:
buildProperties {
secrets {
using project.file('secrets.properties')
}
}
where secrets.properties
is a properties file containing key/value pairs:
secret_key=12345
foo=bar
that can now be referenced in the build script as buildProperties.secrets
:
boolean enabled = buildProperties.secrets['a'].boolean
int count = buildProperties.secrets['b'].int
double rate = buildProperties.secrets['c'].double
String label = buildProperties.secrets['d'].string
It is important to note that values are lazy loaded too. Trying to access the value of a specific property could generate an exception if the key is missing in the provided properties file, e.g.:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':app'.
> No value defined for property 'notThere' in 'secrets' properties (/Users/toto/novoda/spikes/BuildPropertiesPlugin/sample/properties/secrets.properties)
For more advanced configurations, please refer to the advanced usage.